Skip to main content
Glama

FindAgent

by cloud.findagent
OverviewDiscussionsAdmin

findagent_new_version

Publish a NEW VERSION of YOUR OWN agent — whichever kind it is. Call this when a creator asks to update, re-publish, re-pull, re-scan or bump their agent; you do NOT need to know which mechanism its kind uses, because this routes on the agent's own published manifest using the same classifier the web dashboard branches on. An agent built here is re-versioned from the fields you pass (system_prompt / tools / guardrails / example_prompts / llms / credential_slots, exactly as findagent_bump_version takes them) — or, for an ACTION agent, from repo: pass the GitHub repo (owner/name, one you can write to) and its findagent.json is read server side, so a large tool array never has to be re-typed; an agent built from a code or skills repo is re-pulled from its connected GitHub repo (optional ref) — a skills agent that was UPLOADED rather than imported from GitHub has no repo and publishes its next version by uploading on the web dashboard, which this tool answers with that instruction; an mcp-server listing the buyer reaches over the network is re-scanned at that endpoint, while one the buyer runs on their own machine has no endpoint to scan and is re-versioned from the fields you pass, like an agent built here. Pass bump (patch|minor|major, default patch) and a changelog where the kind takes one; the bump is applied to the LISTING's current version, never to a version declared in a repo — the listing owns its own version line, so a hand-edited repo version does not change what publishes here. Owner-only; the new version enters the normal review gate. PREFER THIS over findagent_bump_version / findagent_repull / findagent_reintrospect_mcp — those still work and each refuses a kind it does not handle, which is the mistake this tool removes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoAgents built from a repo only: a branch, tag or commit sha to re-pull. Ignored otherwise.
bumpNoSemver step. Default patch.
repoNoAction agents (kind mcp-tool) only: re-version FROM this GitHub repo (owner/name, one you can write to) — its findagent.json (or a manifest.json declaring schema_version 1.1) supplies the whole tool surface server side, so no tool array passes through a model. Omit it to pass the fields instead.
slugYesYour agent slug (you must own it).
changelogNoWhat changed (10-500 chars), for the kinds that take one.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / repo / description
      Previous value: -"Action agents (kind mcp-tool) only: re-version FROM this GitHub repo (owner/name, one you can write to) — its findagent.json supplies the whole tool surface server side, so no tool array passes through a model. Omit it to pass the fields instead."New value: +"Action agents (kind mcp-tool) only: re-version FROM this GitHub repo (owner/name, one you can write to) — its findagent.json (or a manifest.json declaring schema_version 1.1) supplies the whole tool surface server side, so no tool array passes through a model. Omit it to pass the fields instead."
  2. Changed2 schema fields changed
    • changedInput schema / properties / ref / description
      Previous value: -"Agents built from a code or skills repo only: a branch, tag or commit sha to re-pull. Ignored otherwise."New value: +"Agents built from a repo only: a branch, tag or commit sha to re-pull. Ignored otherwise."
    • addedInput schema / properties / repo
      Added value: +{
+  "description": "Action agents (kind mcp-tool) only: re-version FROM this GitHub repo (owner/name, one you can write to) — its findagent.json supplies the whole tool surface server side, so no tool array passes through a model. Omit it to pass the fields instead.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / ref / description
      Previous value: -"code-bundle / skills-bundle only: a branch, tag or commit sha to re-pull. Ignored for other kinds."New value: +"Agents built from a code or skills repo only: a branch, tag or commit sha to re-pull. Ignored otherwise."
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint=false / openWorldHint=false annotations by disclosing owner-only access, the review gate on the new version, per-kind routing behavior, and the non-obvious rule that the bump applies to the listing's version line and never to a repo-declared version. For a mutation tool this is unusually complete.

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

Conciseness3/5

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

Front-loads the core action well, but it is a single dense paragraph of long em-dash-clause sentences that is harder to parse than necessary. Most clauses carry real information given the multi-kind routing, but the wall-of-text structure costs it readability.

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 an output schema present, return values need not be explained, and the description covers everything else an agent needs: routing across built/action/code/skills/mcp-server kinds, the uploaded-skills edge case that must go to the web dashboard, and the ownership/review constraints.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: `repo` supplies the whole tool surface without passing a tool array through a model, `ref` only applies to repo-built agents, and `bump` targets the listing version rather than a repo version.

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: 'Publish a NEW VERSION of YOUR OWN agent.' It immediately distinguishes itself from siblings by naming findagent_bump_version, findagent_repull, and findagent_reintrospect_mcp and explaining that this tool supersedes their per-kind branching.

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?

Explicit invocation trigger ('Call this when a creator asks to update, re-publish, re-pull, re-scan or bump their agent') plus an explicit preference rule: 'PREFER THIS over findagent_bump_version / findagent_repull / findagent_reintrospect_mcp.' It also states the owner-only precondition and the review-gate consequence.

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