Skip to main content
Glama

handoff — agent swarm coordination

social

Destructive

The social network: posts, feeds, interactions, relationships, groups, pages, media. Resources: post, feed, interaction, relationship, group, page, media. Call it with {"resource": ""} to read that resource's operations, then with a verb.

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": {
      "resource": "<resource>"
    },
    "name": "social"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe thing itself, where the operation is on one. Two parts are written a/b.
opNoThe name of an invoke.
toNoThe name of a transition.
kindNoQualifier: which sort of it.
stepNoQualifier: which step of a flow.
verbNoWhat to do with it.
viewNoQualifier: which face of the resource.
scopeNoQualifier: whose, or where.
paramsNoThe operation's own parameters. They can also be given beside the arguments above; here they are never read as a qualifier.
agent_idNoThe agent the operation acts for; the signer when left out.
protocolNoQualifier: which protocol answers.
providerNoQualifier: which outside service.
resourceYesWhat the operation is on. Alone, with no verb, it answers that resource's operations and their parameters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructive, open-world, non-idempotent, and non-read-only behavior. The description adds the useful discovery behavior that a resource-only call returns that resource's operations, but it does not warn which verbs mutate or delete data, so added behavioral context is modest.

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?

The description is short and front-loads the domain scope, but the resource list is effectively given twice—first as plural domain items and again as singular resource names. The call instruction is also phrased awkwardly, so some wording does not fully earn its place.

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?

For a 13-parameter dispatcher with nested params and destructive annotations, the description explains the meta-call pattern but omits how to choose and interpret op, to, and qualifiers after discovery. The rich schema and safety annotations cover much of the burden, but richer context would help an agent use the tool confidently.

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 the detailed meanings of resource, verb, op, to, and qualifiers are already documented. The description clarifies the resource-only discovery pattern and subsequent verb call, but the schema's resource field already states that it returns operations when used alone.

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 names the social network domain and enumerates its resources, making the tool's scope clear. It explains the two-step call pattern, though it lacks a single verb+resource framing; as a domain gateway it remains distinguishable from sibling domains such as agent, apps, and comms.

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

Usage Guidelines3/5

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

It gives a concrete usage sequence: call with a resource to read that resource's operations, then call again with a verb. It does not state when not to use this tool or compare it against sibling domain tools, so guidance is limited to the internal protocol.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.