Skip to main content
Glama

FindAgent

by cloud.findagent
OverviewDiscussionsAdmin

findagent_create_remote_mcp

List an EXTERNAL remote MCP server you run as a marketplace LISTING — for an MCP server hosted on YOUR OWN infrastructure that buyers connect their client straight to (FindAgent never proxies or runs it). Pass the listing basics (title/slug/tagline/description + example_prompts: 1–5 required; a listing is not categorised, so any category you send is ignored) and the remote endpoint as server_url (https) OR a parsed server.json object in server_json. The server's tools are auto-detected (a sandbox-gated live scan when available) — you can override with tools (name+description), transport (streamable-http|sse), and auth_note (what credential the server needs — NEVER a secret value). Creates a status=draft agent you own; then call findagent_submit_for_review IN THIS MCP CLIENT to submit it. The server URL is stored + displayed only; nothing executes on FindAgent. Before calling: findagent_check_slug + findagent_list_categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
llmsNoOptional target clients. Defaults to ['claude','chatgpt','gemini'].
slugNoPermanent URL slug, kebab-case (3–60, no leading/trailing hyphen). Verify with findagent_check_slug.
tagsNoOptional (≤10). Free-form lowercase tags.
titleNoListing name (3–80 chars).
toolsNoOptional descriptive tools the server exposes ({ name, description }) — SEO/discovery only, no action. Auto-detected when omitted.
taglineNoOne-line value prop (10–140).
auth_noteNoOptional. What credential the server requires (e.g. "Requires a Bearer API key"). DEFINITION only — NEVER a secret value.
transportNoOptional MCP transport. Defaults to streamable-http (auto-detected from server.json).
server_urlNoThe remote MCP endpoint (https). Required unless server_json carries it.
descriptionNoWhat the server does / who it is for (50–4000).
server_jsonNoOptional parsed server.json (registry shape) — used INSTEAD of server_url.
category_slugNoIgnored. A listing is not categorised; the platform files its own placeholder.
example_promptsNoREQUIRED — 1 to 5 concrete things a user can ask this server to do.
additional_category_slugsNoIgnored (a listing is not categorised).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
slugNo
statusNo
accountNo
createdNo
next_toolNo
preview_urlNo
instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / additional_category_slugs / description
      Previous value: -"Optional (≤12). Subcategory under every top-level you select."New value: +"Ignored (a listing is not categorised)."
    • changedInput schema / properties / category_slug / description
      Previous value: -"The PRIMARY category: a TOP-LEVEL slug from findagent_list_categories (≥1 discipline; put subcategories in additional_category_slugs)."New value: +"Ignored. A listing is not categorised; the platform files its own placeholder."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, but the description adds substantial context beyond them: the object is created as a status=draft, the server URL is 'stored + displayed only; nothing executes on FindAgent', tools are auto-detected via a sandbox-gated live scan with override capability, and auth_note must never carry a secret. This is rich, non-redundant behavioral disclosure.

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 scoping statement and the create-vs-submit flow are front-loaded, and almost every clause carries information. It is dense and slightly run-on in the middle (the detection/override sentence), but nothing is 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?

For a 14-parameter tool with nested objects, enums, and an output schema, the description covers what the agent must know: draft state, non-execution guarantee, auto-detection vs override, secret-handling rule, and the mandatory next call. Return values are delegated to the output schema, which is correct.

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 the baseline is 3, but the description adds meaning: it clarifies that server_url and server_json are alternatives, that example_prompts are 1-5 and required, that tools/transport/auth_note are overrides of auto-detection, and explains WHY category fields are ignored ('a listing is not categorised'). That reasoning goes beyond the schema's bare 'Ignored'.

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+resource ('List an EXTERNAL remote MCP server ... as a marketplace LISTING') and crisply scopes it to MCP servers hosted on your own infrastructure that buyers connect to directly. It explicitly distinguishes itself from the draft/package/code-draft siblings by being the remote-MCP listing path, so an agent can pick it without opening schemas.

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?

Explicitly says when to use it (external remote MCP server you host, never proxied by FindAgent), what it produces (status=draft agent you own), and the follow-up step ('call findagent_submit_for_review in this MCP client'). It also names prerequisites to run first (findagent_check_slug + findagent_list_categories).

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

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