FindAgent

findagent_create_code_draft

Persist a CODE-BUNDLE draft from YOUR OWN GitHub repo — for an agent that ships RUNNABLE code (use this when findagent_import_repo returned grounding.code_bundle). Pass the basics (title/slug/tagline/description/category_slug + example_prompts: 1-5 required) + the detected contract from import_repo's grounding.code_bundle (runtime, entrypoint {path,export}, mcp {mode,command,args}, ui {path}, allowed_hosts, credential_slots, skills), overriding any you want to correct. The server RE-PULLS the repo (your stored GitHub token — private repos work, server-side), snapshots + scans the code, validates the manifest, and creates a status=draft agent you own; then call findagent_submit_for_review IN THIS MCP CLIENT to set price + confirm originality/prohibited + submit it (the web is only an optional preview). IDEMPOTENT BY REPO: if you already have a draft for this repo, calling this again OVERWRITES that same draft (basics + manifest + a fresh re-pull/re-scan) instead of creating a duplicate — so iterate freely (the response updated flag is true on overwrite). NEVER send secret credential VALUES — credential_slots declare shape (ref/env/label/allowed_hosts/type) only. Building/running the code stays gated until an admin approves it.

Input Schema

TableJSON Schema

Name	Required	Description
`ui`	No	Optional static UI: { path: bundle-relative index.html }.
`mcp`	No	MCP exposure: { mode: 'wrap'\|'native', command?, args? }. 'native' requires the command that starts the bundle's own MCP server. Defaults to wrap.
`ref`	No	Optional branch/tag/SHA. Defaults to the default branch HEAD.
`llms`	No	Optional target clients. Defaults to ['claude','chatgpt','gemini'] when omitted.
`repo`	No	owner/repo or a github.com URL — YOUR repo (readable by your connected GitHub token). Re-pulled server-side, so private repos you own work.
`slug`	No	Permanent URL slug, kebab-case (3–60, no leading/trailing hyphen). Verify with findagent_check_slug first.
`tags`	No	Optional (≤10). Free-form lowercase tags ([a-z0-9- ]).
`title`	No	Agent name (3–80 chars).
`skills`	No	Optional discovery metadata (the tools the agent exposes). Each: { id?, name, description? }. Never executed.
`runtime`	No	From grounding.code_bundle.runtime: { kind: 'node'\|'python', version? }. Defaults to node.
`tagline`	No	One-line value prop (10–140).
`languages`	No	Optional (≤20). Language/Framework slugs from findagent_list_tech_facets (software-development discipline only).
`entrypoint`	No	From grounding.code_bundle.entrypoint: { path: bundle-relative module, export: handler name }.
`description`	No	What it does / who it is for (50–4000).
`serve_modes`	No	How the code runs when a buyer connects it. 'hosted' = FindAgent runs it in an isolated sandbox over the gateway (the DEFAULT — omit for this). 'local' = the buyer downloads and runs it on their OWN machine via @findagent/mcp so it can reach their localhost/local tools; FindAgent never runs it (the buyer trusts you, like a local MCP server). Pass ['hosted','local'] to offer BOTH. Only set this for an agent that must reach the buyer's own machine — an agent whose credential targets a localhost host CANNOT be served hosted. NOTE: this call OVERWRITES the draft's serve modes — when re-calling for an existing draft, re-send serve_modes to keep a prior 'local'/'both' choice (omitting it resets to hosted-only).
`tech_domains`	No	Optional (≤20). Tech Domain slugs from findagent_list_tech_facets (software-development discipline only).
`allowed_hosts`	No	Default-deny egress allowlist — the ONLY hosts the sandbox may reach. From grounding.code_bundle.allowed_hosts.
`category_slug`	No	The PRIMARY category: a TOP-LEVEL slug from findagent_list_categories (a discipline is required — usually 'software-development'). Put the required subdiscipline (and any industry + subindustry) in additional_category_slugs.
`example_prompts`	No	REQUIRED — 1 to 5 concrete things a user can ask this agent to do (what a real user would type).
`credential_slots`	No	Optional. Each item declares the SHAPE of a secret (ref/env/label/allowed_hosts…) — see `items`. DEFINITIONS ONLY — no values.
`additional_category_slugs`	No	Optional (≤12). Extra slugs from findagent_list_categories. For EVERY top-level you select you MUST include one of its OWN subcategories here: a subdiscipline under your discipline, and (optionally) an industry top-level plus one of its subindustries. This is also where a discipline goes if your primary is an industry.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No
`slug`	No
`bundle`	No
`status`	No
`account`	No
`created`	No
`updated`	No
`next_tool`	No
`preview_url`	No
`instructions`	No

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries the behavioral burden; it discloses server-side re-pull with the stored GitHub token, snapshot/scan/validation, status=draft ownership, idempotent overwrite with an 'updated' flag, and the admin-approval gate. It also clarifies that credential_slots only declare shape and never carry secret values, which is critical safety context. No contradictions with 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.

Conciseness5/5

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

Six dense sentences, each delivering a distinct fact: purpose/condition, payload composition, execution behavior, idempotency, secret policy, and gating. The description is front-loaded and free of filler; heavy use of caps and parentheses packs information efficiently. Given the tool's 21-parameter complexity and nested objects, the length is justified.

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?

With 21 parameters, nested objects, and an output schema, no description can enumerate everything, but this one supplies the missing workflow glue: where input values come from, how to override them, the required next call, and the overwrite semantics. It even notes the 'updated' response flag. Nothing essential for correct invocation is absent.

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% with detailed per-parameter descriptions, so the baseline is 3. The description adds a valuable grouping (basics vs. the detected contract from import_repo's grounding.code_bundle) and the notion of overriding detected values, plus the 'example_prompts required' rule. This is meaningful but largely reinforces and organizes what the schema already states, so it does not reach 5.

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?

The description opens with 'Persist a CODE-BUNDLE draft from YOUR OWN GitHub repo', a specific verb plus resource, and immediately ties it to the condition 'use this when findagent_import_repo returned grounding.code_bundle'. This clearly distinguishes it from the sibling findagent_create_draft and any generic draft tool. No interpretation is left to the agent.

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?

It explicitly states when to use the tool (after import_repo returns grounding.code_bundle) and what to do next ('then call findagent_submit_for_review IN THIS MCP CLIENT'), including the idempotency-driven iteration workflow. It also gives safety guidance on when NOT to send secret values. The alternative for non-code-bundle drafts is implied rather than named, but the precondition is an unambiguous discriminator.

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?