Accept or reject pending friend requests by supplying the friendship ID and choosing accept or reject. Resolve incoming collaboration requests directly within Trackfusion.
Accept or reject a pending friend request
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Accept or reject the request | |
| friendshipId | Yes | Friendship ID from list_friend_requests |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries full burden for behavioral disclosure. It states the core action (accept/reject) but does not disclose consequences such as whether accepting creates a friendship, whether rejecting is reversible, what happens to related data, or error behavior for invalid IDs. This is a significant gap for a state-changing tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single efficient sentence that front-loads the action and target resource. There is no wasted wording, and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter tool with no output schema, the schema plus description likely enables a correct call. However, missing behavioral context (side effects, error states) and lack of usage guidance mean the definition is only minimally complete rather than fully self-sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: both parameters have descriptions, including the action enum values and the source of friendshipId. The description adds no additional parameter meaning beyond what the schema already provides, so the baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Accept or reject a pending friend request' uses a specific verb (accept/reject) and resource (pending friend request). This distinguishes it from siblings like send_friend_request and delete_friend, which handle different stages of the friendship lifecycle.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'pending friend request' and the friendshipId description 'from list_friend_requests' imply the intended workflow: list requests first, then respond. However, there is no explicit guidance on when to use this tool versus send_friend_request or delete_friend, nor any exclusions or alternatives mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.