FindAgent

findagent_get_agent

Read-only

Get the full store view of ONE published FindAgent marketplace agent by slug — mirrors the website's agent detail page. Returns title, tagline, description, price_type/price_cents/currency, category list (omitted for an MCP server listing, which is not categorised), rating, install count, kind, a summary of its tools/skills, example prompts, and a connect hint. is_mcp_server_listing says whether this row is an MCP server FindAgent merely LISTS (connect your client straight to the provider — see connection, hosted or local) rather than an agent FindAgent runs; kind is mcp-tool for both, so it cannot tell them apart. That field is OMITTED when it could not be determined — read its absence as unknown, never as false. A paid agent's tools/skills stay hidden until purchase. For YOUR OWN agent, each tool also carries its action (the prompt template, or an http action's method + url + body template), so a publish can be verified by read-back — a template-only republish is otherwise invisible here. A caller who does not own the agent never sees action, and an http action's headers and auth_ref are withheld from everyone. An unknown or unpublished slug returns a needs_input result pointing back to findagent_browse_agents.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The published agent slug (from findagent_browse_agents).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No
`slug`	No
`title`	No
`tools`	No
`rating`	No
`skills`	No
`tagline`	No
`category`	No
`currency`	No
`categories`	No
`connection`	No
`price_type`	No
`description`	No
`price_cents`	No
`price_label`	No
`connect_hint`	No
`review_count`	No
`install_count`	No
`example_prompts`	No
`is_mcp_server_listing`	No
`paid_capabilities_gated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

addedOutput schema / properties / tools / items / properties / action

Added value: +{
+  "properties": {
+    "body_template": {
+      "type": "string"
+    },
+    "method": {
+      "type": "string"
+    },
+    "template": {
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "prompt-template",
+        "http"
+      ],
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 12, 2026
- addedOutput schema / properties / connection
```
Added value: +{
+  "enum": [
+    "hosted",
+    "local"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / is_mcp_server_listing
```
Added value: +{
+  "type": "boolean"
+}
```
Changed1 schema field changedSep 10, 2026
- addedOutput schema / properties / price_label
```
Added value: +{
+  "type": "string"
+}
```
First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the is_mcp_server_listing omission semantics ('read absence as unknown, never false'), that paid agents hide tools/skills until purchase, that action is visible only to owners, and that http headers/auth_ref are withheld. These are exactly the gotchas an agent needs.

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?

Purpose and return shape are front-loaded, then caveats follow in dense but information-bearing sentences. It is long, but nearly every clause carries a distinct behavioral fact rather than padding.

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?

For a read tool with an output schema present, the description need not explain return values yet still enumerates them and covers the ownership/auth/omission edge cases that the schema and annotations cannot express. Nothing needed to call it correctly is missing.

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 coverage is 100% and the single slug parameter is fully documented in the schema, so the description adds no syntax or format detail. It only reiterates the source ('by slug'), matching the baseline for a schema-complete parameter.

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 store view of ONE published FindAgent marketplace agent by slug') and grounds it with an analogy to the website's agent detail page, cleanly separating it from the list-oriented sibling findagent_browse_agents.

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

Usage Guidelines4/5

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

Explicitly handles the failure path (unknown/unpublished slug returns a needs_input result pointing back to findagent_browse_agents), which routes the agent correctly. It does not compare itself against siblings like list_my_agents or load_listing_tools, so it stops short of full when/not guidance.

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

All FindAgent 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?