Comunio MCP

Completed transfers

get_transfers

Read-only

Retrieve completed transfers with actual paid prices to calibrate your bids. See what players really went for, including quoted prices and settlement details.

Instructions

Get transfers that have already completed, newest first, with what was actually paid.

This is settled prices rather than quotes: what players really went for in this league. Use it to calibrate a bid, since the market only says what a player is listed at. Each transfer also carries quoted_price, what the player was valued at, so paying over or under the odds is visible without another call.

from_computer means bought from Comunio, to_computer sold back to it, and involves_me marks the signed-in manager's own deals. offered_at is when the bid went in and settled_at when it went through. summary totals each kind and the money that changed hands.

limit caps how many transfers come back and defaults to 20, which is a default rather than a maximum: this endpoint returns as many as it is asked for. Raise it to look further back — a larger value costs one extra request only when there is more history than one page holds.

Read-only: fetches history and changes nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No

Output Schema

TableJSON Schema

Name	Required	Description
`summary`	Yes
`has_more`	Yes	Whether older transfers exist beyond what was fetched
`transfers`	Yes	Newest first

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Sep 9, 2026

TDQS

A5/5.0

Behavior5/5

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

The description explicitly discloses behavior beyond the readOnlyHint annotation: it is stated as 'Read-only: fetches history and changes nothing', which reinforces the annotation. It also elaborates on the `limit` parameter's default behavior, clarifying that it is a default, not a maximum, and explains that a larger value may cost one extra request when history exceeds one page. This adds valuable behavioral context that is not apparent from the schema alone.

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?

The description is well-structured and front-loaded with the primary purpose. It uses clear paragraphs to explain the tool's purpose, field meanings, and parameter behavior without redundancy. Every sentence serves a purpose, adding new information rather than restating what the title or schema already provides. It is concise yet comprehensive.

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

Completeness5/5

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

Given the tool's simplicity (one optional parameter) and the presence of an output schema (which the description does not need to repeat), the description is complete. It explains the tool's purpose, usage context, field semantics, and parameter behavior. It provides all necessary information for an agent to call the tool correctly and interpret results, even without seeing the output schema.

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

Parameters5/5

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

Although the schema has 0% description coveragehol, the description provides rich context for the `limit` parameter, explaining its default, that it is not a maximum, and the potential request cost implications. This goes beyond the schema's basic type and default, giving the agent a clear understanding of how to use the parameter effectively. The description effectively compensates for the lack of schema-level descriptions.

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 clearly states what the tool does: it retrieves completed transfers with settled prices rather than quotes. It distinguishes itself from related market tools by emphasizing the 'actual paid' price, which is a specific and meaningful differentiator. This is a clear and specific verb+resource statement.

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

Usage Guidelines5/5

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

The description explicitly explains when to use this tool: to calibrate a bid based on actual market prices, contrasting with the market's listed quotes. It also explains the meaning of each field, such as `from_computer` and `to_computer`, which guides correct interpretation. This provides clear context for how the tool fits into the workflow and when it should be chosen over alternatives.

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