Skip to main content
Glama

List rosters friends lent you

list_borrowed_rosters
Read-onlyIdempotent

Lists rosters the signed-in player has borrowed from friends. Use a borrowed roster’s id to field or seal it where the site allows. Requires mcp:read.

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": "list_borrowed_rosters"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds value beyond that with the permission requirement ('Requires mcp:read') and the caveat that fielding/sealing only works 'where the site allows', signalling site-level restrictions. It stops short of describing return size or pagination.

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?

Two short sentences with zero filler, the resource scope front-loaded and the auth requirement trailing. Everything stated earns its place.

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?

For a read-only listing tool with rich annotations and no output schema, the description covers what is listed, who the subject is, the access prerequisite, and the intended next step. The only gap is result-set behavior (completeness/pagination), which is minor here.

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% and both parameters (llm_model, conversation_id) are analytics metadata, already fully self-documented as optional. The description adds no parameter meaning, but none is needed; baseline 3 applies.

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?

The description names a specific verb and resource with an explicit scope: 'Lists rosters the signed-in player has borrowed from friends.' The qualifier 'borrowed from friends' distinguishes it from siblings like list_my_rosters and list_public_rosters without needing to name them.

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 explains downstream usage ('Use a borrowed roster's id to field or seal it where the site allows'), which implies this is the discovery step before fielding a borrowed list. However, there is no explicit when-to-use versus alternatives guidance, e.g. no routing to list_my_rosters for owned rosters or list_public_rosters for public ones.

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