Skip to main content
Glama

t2000_sentinel_info

Retrieve detailed information about a specific Sui Sentinel, including its model, system prompt, prize pool, and attack history using its ID.

Instructions

Get detailed info about a specific Sui Sentinel — model, system prompt, prize pool, attack history. Use the sentinel ID or object ID from t2000_sentinel_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSentinel agent ID or object ID

Implementation Reference

  • The tool 't2000_sentinel_info' is defined and implemented here, using `agent.sentinelInfo(id)` to fetch data.
    server.tool(
      't2000_sentinel_info',
      'Get detailed info about a specific Sui Sentinel — model, system prompt, prize pool, attack history. Use the sentinel ID or object ID from t2000_sentinel_list.',
      { id: z.string().describe('Sentinel agent ID or object ID') },
      async ({ id }) => {
        try {
          const s = await agent.sentinelInfo(id);
          return { content: [{ type: 'text', text: JSON.stringify({
            ...s,
            attackFee: s.attackFee.toString(),
            attackFeeSui: Number(s.attackFee) / 1e9,
            prizePool: s.prizePool.toString(),
            prizePoolSui: Number(s.prizePool) / 1e9,
          }) }] };
        } catch (err) {
          return errorResult(err);
        }
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. While it mentions what information is returned, it doesn't disclose behavioral traits like whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or response format. The description provides some context but leaves significant behavioral aspects 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?

Two sentences with zero waste. The first sentence clearly states purpose and scope, the second provides essential usage guidance. Every word earns its place with no redundancy or unnecessary elaboration.

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 single-parameter read operation with no output schema, the description adequately covers purpose and basic usage. However, it lacks information about return format, error handling, and behavioral constraints that would be important for an agent to use this tool effectively. The description is complete enough for basic understanding but has clear gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents the single parameter. The description adds minimal value by specifying that the ID can be either 'sentinel ID or object ID from t2000_sentinel_list', which provides slightly more context than the schema's generic description. Baseline 3 is appropriate when schema does most of the work.

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 'Get' and the resource 'detailed info about a specific Sui Sentinel', specifying the exact fields returned: model, system prompt, prize pool, attack history. It distinguishes from sibling t2000_sentinel_list by focusing on a single sentinel's details rather than listing all sentinels.

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

Usage Guidelines4/5

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

The description explicitly states when to use this tool: to get detailed info about a specific sentinel using an ID from t2000_sentinel_list. It provides clear context but doesn't explicitly mention when NOT to use it or alternatives beyond the implied distinction from the list tool.

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