Skip to main content
Glama

Lend a roster to a friend

lend_roster

Lets a friend use an owned roster. Get the roster id from list_my_rosters and the borrower id from list_my_opponents. Confirm the roster and recipient. Requires mcp:manage.

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": {
      "id": "<id>",
      "borrowerId": "<borrowerId>"
    },
    "name": "lend_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
borrowerIdYes
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds one genuinely useful behavioral fact, 'Requires mcp:manage', but does not say what the borrower actually gains, whether the loan is revocable or time-limited, or what a self-lend would do.

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

Conciseness5/5

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

Three short sentences, each doing distinct work: capability, prerequisite lookups, confirmation step, permission requirement. Nothing is repeated or padded.

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 mutating, open-world tool with no output schema, the definition covers preconditions and auth but leaves out the observable effect of the call, loan limits, and how to undo it (end_roster_loan). Adequate but with clear gaps.

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 50%: id and borrowerId have no schema descriptions, and the description usefully explains where each comes from. The remaining parameters are documented in the schema itself. The description adds real value for the undocumented IDs but no constraints or formats beyond provenance.

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?

States a specific verb and resource: 'Lets a friend use an owned roster.' That is clearly distinct from siblings like copy_roster or delete_roster, though it never names end_roster_loan, the tool that reverses it.

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?

Gives concrete prerequisites and routing: roster id from list_my_rosters, borrower id from list_my_opponents, plus a 'confirm the roster and recipient' step before acting. There is no explicit when-not-to-use guidance or pointer to the counterpart tool for revoking a loan.

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.

Resources