FindAgent

findagent_list_my_agents

Read-only

List the agents that are YOURS, in either sense. scope:"created" (the default) returns agents you CREATED — id + slug + name + kind + status + any in-flight re-version status — plus your personal departments; call it FIRST when you need a slug for a lifecycle tool (findagent_edit_price / findagent_bump_version / findagent_withdraw_version / findagent_edit_metadata / findagent_rollback_version), to submit a draft (findagent_submit_for_review — a draft/needs_changes agent is submittable), or to attach a knowledge base (findagent_attach_kb). scope:"acquired" returns agents you BOUGHT or INSTALLED — your library — which is what to call when a buyer asks what they have access to; those are not yours to edit. An acquired row carries update_awaiting_your_approval:true when a newer version asks for more permissions than were accepted and the buyer has not approved it yet, so they are still being served the earlier version (approval is given on the agent page). scope:"all" returns both. Essential after reconnecting in a new session, when you no longer have the slug of something you created or acquired earlier. READ-ONLY.

Input Schema

Name	Required	Description	Default
`scope`	No	Which sense of "mine": created (default — agents you authored, editable via the lifecycle tools), acquired (agents you bought or installed, read-only to you), or all.

Output Schema

Name	Required	Description	Default
`agents`	No
`acquired`	No
`truncated`	No
`departments`	No
`instructions`	No
`total_agents`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026
- addedOutput schema / properties / total_agents
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedSep 11, 2026

addedInput schema / properties / scope

Added value: +{
+  "description": "Which sense of \"mine\": created (default — agents you authored, editable via the lifecycle tools), acquired (agents you bought or installed, read-only to you), or all.",
+  "enum": [
+    "created",
+    "acquired",
+    "all"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / acquired

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so 'READ-ONLY' is somewhat redundant, but the description adds real behavioral context: acquired agents are not editable, and the update_awaiting_your_approval:true flag means the buyer is still served the earlier version until approval on the agent page. That flag semantics is genuinely non-obvious and not derivable from annotations or schema.

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?

Front-loaded with the core statement and the scope options, and structured around them. It is dense and the parenthetical lists of lifecycle tool names run long, but nearly every clause carries routing or field-semantics information; minor trimming of the tool-name enumerations would improve it.

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?

An output schema exists so return values needn't be explained, yet the description still flags the salient row fields and the one non-obvious flag. For a single-optional-enum read tool, an agent has everything needed to select and invoke it correctly.

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% and the enum is fully documented in-schema, so the baseline is 3. The description goes beyond that by attaching an action consequence to each scope value (created → editable via lifecycle tools; acquired → read-only library), making the choice of scope operationally meaningful rather than just definitional.

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 (list agents) and immediately disambiguates the ambiguous 'mine' into three scopes, with the per-scope payload spelled out (id + slug + name + kind + status). It clearly distinguishes itself from the many lifecycle siblings by positioning itself as the slug-resolution entry point.

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 when-to-use for each scope: 'call it FIRST when you need a slug for a lifecycle tool' with the sibling tools named, 'to submit a draft', 'to attach a knowledge base', and 'call when a buyer asks what they have access to'. It also states a when-not implicitly via 'those are not yours to edit' and names the reconnect-in-a-new-session case.

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

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

Need Help?