Agentropolis

Get one listing's details, trust evidence and price

get_kit

Read-onlyIdempotent

Get the full Agentropolis record for one listing by id: summary, pricing, payment-verified trust evidence (verified buyers, settlements, wash flags, disclosed test sales), badge tiers, sources and links. Use it after search_kits to judge whether a listing is worth using; use get_kit_manifest instead when you need the machine-readable invoke contract (endpoints, schemas, payment offers). Read-only, no auth; logs an anonymous detail view for seller analytics. Unknown ids return an error result with error 'not_found'. Example: {"id":"seenly.seenly-token-preflight"}.

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
`kind`	Yes
`name`	Yes
`tiers`	No	Badge tiers: earned (Verified, Live-Tested, Trusted) and paid/showcase (Agentropolis Pro)
`trust`	No	Payment-verified trust; score null = no evidence
`badges`	Yes

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": {
+    "badges": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "tiers": {
+      "description": "Badge tiers: earned (Verified, Live-Tested, Trusted) and paid/showcase (Agentropolis Pro)"
+    },
+    "trust": {
+      "description": "Payment-verified trust; score null = no evidence"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "kind",
+    "badges"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds genuine non-obvious behavior: an anonymous detail view is logged for seller analytics, and unknown ids return an error result with error 'not_found'. Those are traits the annotations cannot express, though it stops short of describing the response payload structure.

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?

Front-loaded with the core purpose, then usage guidance and routing. Every sentence carries load — returns, routing, side effect, error behavior, example. Slightly dense but no filler.

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

Completeness5/5

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

Output schema is declared, so return-value structure need not be repeated; the description instead covers the behavioral edges an agent needs: read-only/no-auth, analytics side effect, not_found semantics, and sibling routing. Complete for a single-param read tool.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description goes beyond the schema by stating that unknown ids produce a 'not_found' error result and by supplying a concrete example id, which helps an agent construct valid calls rather than just understand the type.

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 full Agentropolis record for one listing by id') and enumerates the returns (summary, pricing, trust evidence, badge tiers, sources, links). It also explicitly names the sibling it is not — get_kit_manifest — so an agent can route between the two 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 workflow trigger ('Use it after search_kits to judge whether a listing is worth using') and an explicit exclusion with the alternative ('use get_kit_manifest instead when you need the machine-readable invoke contract'). Both the when and the when-not are covered.

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

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?