agentek-eth

intentCollectFees

Collect accumulated fees from a Uniswap V3 position by specifying the token ID and chain ID to withdraw earnings to a designated recipient.

Instructions

Collects accumulated fees from a Uniswap V3 position

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": {
      "tokenId": "<tokenId>",
      "chainId": "<chainId>"
    },
    "name": "intentCollectFees"
  }
}

Input Schema

Name	Required	Description	Default
`tokenId`	Yes
`recipient`	No
`chainId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It does not disclose that this is likely a write operation (implied by 'collects'), potential gas costs, authorization needs, or effects on the position, leaving critical behavioral traits unspecified.

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 a single, efficient sentence with zero wasted words. It is front-loaded with the core purpose, making it highly concise and well-structured for quick understanding.

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

Completeness2/5

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

Given the complexity of a blockchain transaction tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on behavior, parameters, outputs, and context needed for safe and effective use, falling short of providing adequate guidance.

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 0%, so the description must compensate but adds no parameter information. It does not explain what 'tokenId', 'recipient', or 'chainId' represent, their formats, or how they affect the operation, failing to provide necessary semantics beyond the bare schema.

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?

The description clearly states the action ('collects') and the resource ('accumulated fees from a Uniswap V3 position'), which is specific and actionable. However, it does not explicitly differentiate from sibling tools like 'intentWithdrawFromSlow' or other fee-related operations, missing an opportunity for precise sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It lacks context on prerequisites (e.g., position must have accumulated fees), exclusions, or comparisons to other tools like 'getPositionDetails' for checking fee amounts, leaving the agent with no usage direction.

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

Deploy Server