Agentropolis

Get one listing's kit.json invoke contract

get_kit_manifest

Read-onlyIdempotent

Get the kit.json v0.1 manifest for one listing: how to call it (HTTP, MCP or A2A endpoints), input/output schema references, payment offers (rail, network, asset, payTo, amount), discovery files and a trust summary. Use it when you are about to call a listing yourself; use get_kit for human-readable details and trust evidence, or call_kit to call an x402 listing through Agentropolis. Read-only, no auth. For seller-published kits this mirrors the seller's own kit.json; for seeded listings it is generated from public metadata and may be incomplete, so prefer the seller's live 402 challenge for exact prices. Example: {"id":"seenly.seenly-pitch-kit"}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Listing id exactly as returned by search_kits results[].id, e.g. 'seenly.seenly-token-preflight' or 'mcp.io-github-owner-name'.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`kit`	Yes	Manifest version, '0.1'
`invoke`	No
`offers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026

addedInput schema / properties / id / description

Added value: +"Listing id exactly as returned by search_kits results[].id, e.g. 'seenly.seenly-token-preflight' or 'mcp.io-github-owner-name'."

addedInput schema / properties / id / minLength
```
Added value: +3
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "invoke": {
+      "items": {},
+      "type": "array"
+    },
+    "kit": {
+      "description": "Manifest version, '0.1'",
+      "type": "string"
+    },
+    "offers": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "required": [
+    "kit",
+    "id"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered; the description still adds value by stating 'no auth' and, more importantly, the provenance caveat that seeded listings are generated from public metadata and may be incomplete, with a pointer to the seller's live 402 challenge for exact prices. It stops short of rate limits or error behavior, but the data-reliability warning is a meaningful disclosure beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and contents are front-loaded, then usage routing, then the provenance caveat, then an example. Every sentence carries information, though the enumeration of manifest fields and the trailing example add mild length for a one-parameter read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers purpose, alternatives, auth, and a reliability caveat for seeded listings. The only minor gap is the absence of any guidance on failure modes (e.g., unknown or malformed listing id), which for a single-required-param lookup would be the last useful addition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single 'id' parameter is fully documented with format guidance and examples. The description's example ({'id':'seenly.seenly-pitch-kit'}) merely restates what the schema already conveys, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the kit.json v0.1 manifest for one listing') and enumerates the payload contents (endpoints, schema refs, payment offers, discovery files, trust summary). It explicitly differentiates itself from the sibling tools get_kit and call_kit, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('when you are about to call a listing yourself') and names two alternatives with their selecting conditions: get_kit for human-readable details and trust evidence, call_kit for invoking an x402 listing. No inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agentropolis tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?