MCP Tool Usage Examples
This tool can be called via the MCP (Model Context Protocol) endpoint. Here are examples of how to use it:
JSON-RPC Call Example:
POST to https://venue-3.covia.ai/mcp
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "covia_inspect",
"arguments": {
"input": "your input here"
}
}
}
cURL Example:
curl -X POST https://venue-3.covia.ai/mcp \\
-H "Content-Type: application/json" \\
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "covia_inspect",
"arguments": {
"input": "your input here"
}
}
}'
Python Example:
import requests
import json
url = "https://venue-3.covia.ai/mcp"
payload = {
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "covia_inspect",
"arguments": {
"input": "your input here"
}
}
}
response = requests.post(url, json=payload)
result = response.json()
print(result)
JavaScript/Node.js Example:
const fetch = require('node-fetch');
const url = 'https://venue-3.covia.ai/mcp';
const payload = {
jsonrpc: '2.0',
id: 1,
method: 'tools/call',
params: {
name: 'covia_inspect',
arguments: {
input: 'your input here'
}
}
};
fetch(url, {
method: 'POST',
headers: {
'Content-Type': 'application/json'
},
body: JSON.stringify(payload)
})
.then(response => response.json())
.then(data => console.log(data));
Asset Metadata
{
"name": "Inspect Lattice Data",
"description": "Primary discovery tool. Budget-bounded JSON5 preview of any lattice path: shows shape, types, sizes, and partial values without overwhelming context. Annotations like {/* +15 more, 102KB */} reveal what was elided so you can decide where to drill in next.\n\nAll paths resolve under your DID as the implicit root. Two kinds of sub-namespaces:\n\nVenue-virtual (read-only, same view for every caller — start here for discovery):\n v/ops/ venue operation catalog (e.g. v/ops/json/merge)\n v/info/ venue introspection (adapters, capabilities)\n\nYour private namespaces (start empty; populated by your writes):\n w/ workspace — read/write structured data\n o/ operation pins — short names for grid_run\n a/ content-addressed assets — immutable blobs by hash\n g/ agents — config, state, timeline, inbox\n n/ named references\n t/ transient/scratch space\n j/ job log — auto-populated by the venue as you invoke ops\n\nFederated:\n did:key:<id>/ another user's namespace (subject to access control)\n did:web:<host>/ another venue\n\nNote: '/' lists only your materialised entries (j/ and anything you've written) — virtual namespaces like v/ resolve on lookup but don't appear in root enumeration. So begin with covia_inspect path=v.\n\nProgressive exploration: covia_inspect path=v budget=400 (venue overview) → covia_inspect path=v/ops/secret budget=2000 (drill down) → covia_read path=v/ops/secret/set (full value when ready). Pass an array of paths to compare multiple values in one call.",
"dateCreated": "2026-04-07T00:00:00Z",
"operation": {
"adapter": "covia:inspect",
"toolName": "covia_inspect",
"input": {
"type": "object",
"properties": {
"paths": {
"description": "A single resolvable path or an array of them. Examples: 'v/info', 'w/vendors', or ['v/ops/json/merge', 'v/ops/json/cond']."
},
"budget": {
"type": "integer",
"description": "Byte budget for the rendered JSON5 output (default 500). Larger budgets show more detail; smaller budgets truncate with structural annotations."
},
"compact": {
"type": "boolean",
"description": "If true, render single-line JSON5 output (default). If false, pretty-print with indentation."
}
},
"required": ["paths"]
},
"output": {
"type": "object",
"properties": {
"result": { "description": "Rendered JSON5 string (single path) or map of path → rendered JSON5 (multiple paths)" }
}
}
}
}