Skip to main content
Glama
mission69b

t2000

by mission69b
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

t2000_positions

View current lending positions across protocols like NAVI and Suilend, including deposits, borrows, and APYs for account monitoring.

Instructions

View current lending positions across protocols (NAVI, Suilend) — deposits, borrows, APYs. For a full account snapshot, prefer t2000_overview instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • packages/mcp/src/tools/read.ts:84-96 (handler)
    The handler for 't2000_positions' which calls 'agent.positions()' and returns the result as text.
    server.tool(
  't2000_positions',
  'View current lending positions across protocols (NAVI, Suilend) — deposits, borrows, APYs. For a full account snapshot, prefer t2000_overview instead.',
  {},
  async () => {
    try {
      const result = await agent.positions();
      return { content: [{ type: 'text', text: JSON.stringify(result) }] };
    } catch (err) {
      return errorResult(err);
    }
  },
);

Tool Definition Quality

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates this is a read-only operation ('View') and specifies the scope (protocols: NAVI, Suilend) and data types returned. However, it doesn't disclose behavioral traits like rate limits, authentication needs, or error conditions, which would be helpful for a tool with no annotations.

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 two sentences with zero waste: the first states the purpose and scope, the second provides usage guidance. It's front-loaded with the core functionality and efficiently structured.

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?

Given the tool has no parameters, no annotations, and no output schema, the description provides good context on what the tool does and when to use it. However, it lacks details on output format or behavioral constraints, which could be important for an agent invoking it. It's mostly complete but has minor gaps.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter information, which is appropriate. A baseline of 4 is applied since it compensates adequately by not introducing unnecessary details.

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 the verb ('View') and resource ('current lending positions across protocols (NAVI, Suilend)') with specific details about what data is included ('deposits, borrows, APYs'). It effectively distinguishes from the sibling tool t2000_overview by specifying this is for positions only, not a full account snapshot.

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 provides when to use this tool ('View current lending positions') and when to prefer an alternative ('For a full account snapshot, prefer t2000_overview instead'). This gives clear guidance on tool selection among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mission69b/t2000'

If you have feedback or need assistance with the MCP directory API, please join our Discord server