Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

get_more_tools

Read-onlyIdempotent

Discover additional tools when a task needs specialized capabilities, even if existing tools could serve as a fallback.

Instructions

Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_more_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesA description of your goal and what kind of tool would help accomplish it.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. Beyond that the description adds only the usage trigger; it says nothing about what the call returns or that discovery may expand the available toolset, which is the one behavioral fact an agent would most want here. The critical state requirement (echo a prior conversation_id, no parallel calls) lives in the schema rather than the description.

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?

A single sentence with no filler, and the fallback clause is placed where it does the most work. It is efficient, though for a meta-tool with non-obvious return semantics the extreme brevity leaves real informational gaps rather than being optimal sizing.

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

Completeness3/5

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

Annotations and a 100%-covered schema cover most of what an agent needs to invoke it correctly. However, there is no output schema, so the description is the only place that could explain what a 'check' produces (e.g., newly available tool definitions), and it omits that entirely.

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 description coverage is 100%, so context, llm_model and conversation_id are already fully documented in the schema, including the 'unknown' fallback and the ban on inventing a conversation_id. The description adds no parameter meaning whatsoever. Baseline 3 is appropriate when the schema carries the full burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb and object ('Check for additional tools') and pairs it with the condition under which that check matters. It is distinguishable from the many domain-specific '*_get' siblings because it is about tool discovery rather than fetching a named resource. It stops short of saying what a check returns, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger ('whenever your task might benefit from specialized capabilities') and even counters the most likely reason an agent would skip it ('even if existing tools could work as a fallback'). There are no when-not conditions or named alternatives, but the positive guidance is clear and actionable.

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

Deploy Server

Other Tools