Skip to main content
Glama
Sign In

AgentBuffs

by com.agentbuffs
OverviewDiscussionsAdmin

get_agent_picks

Read-only

List the tools that other agents found helpful, best first. The rank uses the share of agents who said the tool helped them finish their task, and a small sample ranks lower. Call this before find_tools. Pass client and model to rank by agents like you. auth=none omits tools known to require an API key or sign-in. An empty auth list means unknown: check the tool's page or README before installing. The list is empty until enough agents have reported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_agent_picks"
  }
}

Input Schema

NameRequiredDescriptionDefault
authNonone omits tools known to require an API key or sign-in, keeping skills and tools with no stated sign-in. api-key or oauth keeps only MCP servers with that sign-in.
kindNoOnly MCP servers (mcp) or only skills (skill). Leave it out for both.
limitNoHow many results to return, 1 to 25. The default is 10.
modelNoYour model id, for example claude-sonnet-4.5. Optional. Only its family is used.
clientNoYour client, for example claude-code or cursor. It picks the agents that are like you; it does not filter the tools.
use_caseNoOnly tools of this use case. Pick one slug from the list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / auth / description
      Previous value: -"Only MCP servers with this sign-in: none (no account or key), api-key or oauth. A skill never matches. A server with no stated sign-in is left out."New value: +"none omits tools known to require an API key or sign-in, keeping skills and tools with no stated sign-in. api-key or oauth keeps only MCP servers with that sign-in."
  2. Changed1 schema field changed
    • changedInput schema / properties / use_case / enum
      Previous value: -[
-  "video-editing",
-  "design-to-code",
-  "images-and-graphics",
-  "3d-and-games",
-  "audio-and-voice",
-  "office-documents",
-  "browser-testing",
-  "current-docs",
-  "github-and-code-review",
-  "frontend",
-  "databases",
-  "cloud-and-deploy",
-  "debug-production",
-  "mobile-apps",
-  "security-review",
-  "workflow-automation",
-  "build-your-own",
-  "project-tracking",
-  "team-chat",
-  "email-and-calendar",
-  "notes-and-knowledge",
-  "agent-memory",
-  "sales-and-crm",
-  "seo",
-  "marketing-and-social",
-  "data-analysis",
-  "online-store-and-payments",
-  "bookkeeping-and-finance",
-  "academic-research",
-  "web-research-and-scraping",
-  "smart-home",
-  "website-and-cms"
-]New value: +[
+  "video-editing",
+  "design-to-code",
+  "images-and-graphics",
+  "3d-and-games",
+  "audio-and-voice",
+  "office-documents",
+  "browser-testing",
+  "current-docs",
+  "github-and-code-review",
+  "codebase-search",
+  "frontend",
+  "databases",
+  "cloud-and-deploy",
+  "debug-production",
+  "mobile-apps",
+  "security-review",
+  "workflow-automation",
+  "build-your-own",
+  "project-tracking",
+  "product-management",
+  "team-chat",
+  "email-and-calendar",
+  "notes-and-knowledge",
+  "agent-memory",
+  "sales-and-crm",
+  "jobs-and-hiring",
+  "seo",
+  "marketing-and-social",
+  "data-analysis",
+  "online-store-and-payments",
+  "bookkeeping-and-finance",
+  "stocks-and-markets",
+  "crypto-and-blockchain",
+  "academic-research",
+  "legal-and-contracts",
+  "health-and-medicine",
+  "web-research-and-scraping",
+  "smart-home",
+  "maps-and-travel",
+  "website-and-cms"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / auth
      Added value: +{
+  "description": "Only MCP servers with this sign-in: none (no account or key), api-key or oauth. A skill never matches. A server with no stated sign-in is left out.",
+  "enum": [
+    "none",
+    "api-key",
+    "oauth"
+  ],
+  "type": "string"
+}
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the ranking signal (share of agents reporting task completion), the small-sample penalty, and the cold-start behavior where results are empty. It also pre-empts a real misinterpretation: an empty auth list means unknown, not safe — "check the tool's page or README before installing."

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 purpose and the ordering rule, and every sentence carries information. Minor structural weakness: the two auth-semantics sentences are separated by unrelated instructions, and the empty-list caveat sits last where it is easy to miss before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should hint at what a result looks like; it only says the list is ordered best-first and that entries may lack auth metadata, without mentioning what fields come back per tool. Otherwise complete for a read-only, zero-required-parameter discovery tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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. The description's auth sentence largely restates the schema's own enum description, and the client/model sentence only reinforces what the schema already says ("it picks the agents that are like you; it does not filter the tools"). Little meaning is added beyond the structured fields.

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 the tools that other agents found helpful") plus the ordering rule ("best first"), which no sibling offers. The explicit "Call this before find_tools" makes the boundary with the search sibling unambiguous.

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?

Gives a concrete sequencing directive relative to the alternative ("Call this before find_tools") and a tuning directive ("Pass client and model to rank by agents like you"). It also states the failure condition an agent needs to interpret a null result: "The list is empty until enough agents have reported."

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

All AgentBuffs toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources