Skip to main content
Glama

End a roster loan

end_roster_loan
Destructive

Revokes a loan if the player owns the roster, or returns it if the player is the borrower. Confirm who loses access before calling. 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": "end_roster_loan"
  }
}

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.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavior: the outcome differs by caller role, access is revoked rather than merely flagged, and the call requires the mcp:manage permission. It does not say whether the loan record is deleted or archived, or whether it is reversible, which keeps it short of a 5.

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, zero waste, and the role-dependent outcome plus the safety caution are both front-loaded before the permission note. Nothing could be trimmed without losing information.

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 destructive mutation with no output schema and no annotations covering permission or reversibility, the description does cover auth and the access-loss warning. It is nevertheless incomplete on what state remains after the call and on the meaning of the required identifiers, which an agent needs before invoking it.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the two documented parameters (llm_model, conversation_id) are analytics fields, not the required id and borrowerId, which have no descriptions anywhere. The description supplies no meaning for id (roster id? loan id?) or borrowerId, leaving the agent to guess at the parameters that actually drive the call.

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 (revokes/returns) and resource (a roster loan), and goes further by explaining the role-dependent outcome: owner revokes, borrower returns. An agent can tell this is the counterpart to lend_roster without opening the schema, though no sibling is named explicitly.

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?

"Confirm who loses access before calling" gives a precondition/caution, which is useful implied usage guidance, but there is no explicit when-to-use versus alternatives (e.g. lend_roster to create a loan, get_roster_loans to inspect one). The agent must infer that this is the inverse of lending.

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