Skip to main content
Glama

FindAgent

by cloud.findagent
OverviewDiscussionsAdmin

findagent_bump_version

Publish a NEW version of YOUR OWN published agent built here (instructions, skills and actions) for review. Pass the agent slug + a semver bump (patch|minor|major). You can fully EDIT the new version: system_prompt + example_prompts, AND (for an agent built here) the whole capability surface — pass tools (and optional credential_slots / guardrails) to add/remove/edit tools + action bindings + credential slots, and optional price_type/price_cents to change the price. Any capability change re-runs the same security scan + author-time auth_ref↔host check. changelog is optional when you edit tools (auto-drafted from the diff); otherwise pass 10–500 chars. The new version goes to admin review; your LIVE version keeps serving until it is approved (never auto-unpublished). A price change applies immediately (not retroactive). Owner-only. (Code-bundle agents re-version through the code wizard, not here.) An ACTION agent whose findagent.json lives in a GitHub repo you can write to should NOT take its tool array through this field path: call findagent_new_version (or findagent_repull) with repo instead, so the tools are read server side and never re-typed by a model. This field path stays for edits with no repo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bumpYes
llmsNoTarget clients ⊂ {claude,chatgpt,gemini,cursor,vscode,custom}.
slugYesYour published agent slug (you must own it).
toolsNoOptional FULL action and skill tool set for the new version (web-builder parity). Presence REPLACES the agent's whole tool surface — pass the complete intended list (add/remove/edit); item shape is in `items`. auth_ref must match a credential_slots[].ref whose allowed_hosts cover the action host (audience binding — enforced). Omit to keep the stored tools (prompt-only edit).
changelogNoWhat changed (10–500 chars). Optional when you pass `tools` — then it is auto-drafted from the tool diff; supply your own to override.
guardrailsNoOptional declared guardrails for the new version (you can only TIGHTEN; the platform always applies its mandatory rails). An invalid block fails the bump.
price_typeNoOptional. Change the price alongside the bump. Applies immediately (audited, not retroactive — existing buyers keep access).
price_centsNoRequired when price_type=paid: positive integer of US cents, max 50000 ($500).
system_promptNoThe updated agent instructions. For an agent whose prompt isn't the authoring surface (kind 'mcp-tool' / 'skills-bundle') you may omit it to keep the stored one; otherwise min 50 chars.
example_promptsNoUp to 5 concrete things a user can ask it to do.
credential_slotsNoOptional. The new version’s full credential-slot set when you pass `tools` — item shape is in `items`. DEFINITIONS ONLY — never send secret VALUES.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNo
statusNo
versionNo
changelogNo
instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / system_prompt / description
      Previous value: -"The updated agent instructions. For a doer whose prompt isn't the authoring surface (mcp-tool / skills-bundle) you may omit it to keep the stored one; otherwise min 50 chars."New value: +"The updated agent instructions. For an agent whose prompt isn't the authoring surface (kind 'mcp-tool' / 'skills-bundle') you may omit it to keep the stored one; otherwise min 50 chars."
    • changedInput schema / properties / tools / description
      Previous value: -"Optional FULL doer tool set for the new version (web-builder parity). Presence REPLACES the agent's whole tool surface — pass the complete intended list (add/remove/edit); item shape is in `items`. auth_ref must match a credential_slots[].ref whose allowed_hosts cover the action host (audience binding — enforced). Omit to keep the stored tools (prompt-only edit)."New value: +"Optional FULL action and skill tool set for the new version (web-builder parity). Presence REPLACES the agent's whole tool surface — pass the complete intended list (add/remove/edit); item shape is in `items`. auth_ref must match a credential_slots[].ref whose allowed_hosts cover the action host (audience binding — enforced). Omit to keep the stored tools (prompt-only edit)."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the full behavioral workflow: the new version goes to admin review, the live version keeps serving until approved and is never auto-unpublished, a price change applies immediately but not retroactively, capability changes re-run the security scan and author-time auth_ref↔host check, and guardrails can only be tightened.

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 description is long and dense, but it is front-loaded with purpose and required parameters, then moves through edit capabilities, review behavior, and routing exclusions. Almost every sentence adds operational value, though some parenthetical detail could be tightened.

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, 11 parameters, nested objects, and the existence of an output schema, the description is complete enough for correct invocation. It covers purpose, usage boundaries, mutation behavior, review flow, and security implications without needing to explain return values.

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?

With 91% schema description coverage, the schema already documents most parameters, but the description adds real meaning: `tools` presence replaces the entire tool surface, `changelog` is optional when editing tools and otherwise must be 10–500 chars, `price_cents` requires `price_type=paid`, and `credential_slots` are definitions only. It does not mention the `llms` parameter, but the schema covers it.

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 uses a specific verb and resource: 'Publish a NEW version of YOUR OWN published agent built here (instructions, skills and actions) for review.' It distinguishes this tool from siblings by explicitly naming findagent_new_version and findagent_repull for repo-backed ACTION agents, and the code wizard for code-bundle agents.

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 gives explicit when-to-use and when-not-to-use guidance: use this for an agent built here, but for a code-bundle agent use the code wizard, and for an ACTION agent whose findagent.json is in a writable GitHub repo call findagent_new_version or findagent_repull with `repo` instead. Owner-only is also stated.

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