Skip to main content
Glama
Sign In
tako-mcp

tako-mcp

by arrow2nd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_account_info

Retrieve account information including contract status, electricity supply points, active agreements, product details, and standing charges. Personal address is excluded for privacy.

Instructions

Get account information including contract status, electricity supply points, active agreements, product details and standing charges. Address is excluded for privacy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, description partially transparent: discloses address exclusion for privacy. However, does not mention other behaviors like data freshness, authentication needed, or error scenarios. Could be more thorough.

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 concise sentences with front-loaded purpose. No wasted words; each sentence provides essential information.

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?

For a zero-parameter tool with no output schema, description covers key aspects of what is included and what is excluded. Could mention if it returns current account or multiple accounts, but overall sufficient.

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?

No parameters, so schema coverage is 100%. Description adds meaning beyond schema by detailing what data is returned, giving the agent a clear picture of the output content.

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?

Description uses specific verb 'Get' and resource 'account information', lists included data fields (contract status, electricity supply points, etc.), and notes excluded data (address for privacy). Clearly distinct from siblings get_electricity_consumption and get_postal_areas.

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

Usage Guidelines3/5

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

Implied use when needing account details, but no explicit when-to-use or when-not-to-use compared to alternatives. Lacks guidance on prerequisites or context.

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

Deploy Server

Other Tools