FindAgent

findagent_reintrospect_mcp

Publish a NEW version of YOUR OWN published EXTERNAL MCP-server listing by RE-INTROSPECTING its remote endpoint. FindAgent re-lists the remote server's current tools (over a sandbox-gated, SSRF-hardened scan), compares them to your live listing, and — if the tool surface CHANGED — submits a new version for admin review with an auto-drafted changelog. Your LIVE listing keeps serving until the new version is approved (never auto-unpublished). If the tools are unchanged it is a no-op. If the remote can't be reached / is auth-walled / the scan is unavailable, nothing changes (reported back). Pass the listing slug (you must own it); optional bump (patch|minor|major, default patch) + changelog override. The server URL is read from your stored listing — nothing executes on FindAgent. Owner-only; for external mcp-server listings only (code agents use the code wizard, doers use findagent_bump_version).

Input Schema

TableJSON Schema

Name	Required	Description
`bump`	No	Optional semver bump for the new version. Defaults to patch.
`slug`	Yes	Your published mcp-server listing slug (you must own it).
`changelog`	No	Optional changelog override (≤500 chars). Defaults to an auto-drafted line from the tool diff.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No
`status`	No
`changed`	No
`scanned`	No
`version`	No
`changelog`	No
`scan_note`	No
`server_url`	No
`tool_count`	No
`instructions`	No

TDQS

A4.9/5.0

Behavior5/5

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

Goes far beyond the annotations: describes sandbox-gated SSRF-hardened scanning, that the live listing never gets auto-unpublished, that unchanged tools produce a no-op, and that unreachable/auth-walled endpoints leave state unchanged. Also clarifies nothing executes on FindAgent and that a new version goes to admin review. No contradiction with readOnlyHint=false and destructiveHint=false.

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

Conciseness5/5

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

Dense but front-loaded: the first sentence states the exact operation and object, and later sentences each add a distinct behavioral constraint (no-op, no auto-unpublish, auth-wall failures). Length is justified by the number of safety-relevant details; no filler or redundancy.

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?

Given the tool's complexity (review workflow, no-op, failure modes, ownership, compatibility scope) and the presence of an output schema, the description covers every decision-relevant dimension. An agent can determine whether to call it and what will happen in all named outcomes.

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 already covers all 3 parameters at 100%, so baseline is 3. Description adds useful nuance: slug must be owned, server URL is read from the stored listing, bump defaults to patch, and changelog overrides the auto-draft. This lifts it above baseline.

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?

Clearly identifies a specific action: publish a new version of an external MCP-server listing by re-introspecting its remote endpoint. It distinguishes from sibling tools like findagent_bump_version (for doers) and the code wizard, and references the owned-slug requirement. The verb and resource are unambiguous.

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?

Provides explicit applicability: owner-only, external mcp-server listings only, and explicitly routes code agents to the code wizard and doers to findagent_bump_version. It also describes no-op and failure conditions that tell the agent when calling is pointless (unchanged tools, unreachable remote). This is strong alternative-routing 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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Every tool targets a clearly scoped resource+action combination, and the versioning variants (bump_version vs repull vs reintrospect_mcp) are explicitly disambiguated by agent kind. Even with 52 tools, the descriptions make each purpose distinct enough to avoid misselection.

Naming Consistency4/5

Nearly all tools follow the findagent_<verb>_<object> snake_case pattern, and families share predictable verbs like list, create, delete, edit, and submit. Minor exceptions such as findagent_preflight, findagent_whoami, and findagent_earnings keep it from perfect consistency.

Tool Count2/5

At 52 tools, this far exceeds the 25-tool threshold for a coherent MCP surface. The count may reflect a broad platform, but as a single toolset it is heavy and likely to strain agent selection and context.

Completeness3/5

The surface covers publishing, versioning, knowledge bases, org management, GitHub import, purchases, and the demand board in impressive depth. However, there are notable dead ends: no unpublish/delete for a live agent, no request-fulfillment/linking action, and no org deletion or KB document update.

Resources

Need Help?