u2-mcp

by bpamiri

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

get_account_info

Retrieve metadata about your current Universe account, including available files, VOC entries, and system details.

Instructions

Get information about the current Universe account.

Returns account-level metadata including available files, VOC entries, and system information.

Returns: Dictionary containing account information, file list, and system details.

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

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jul 30, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only describes return content but does not mention that the tool is read-only, has no side effects, or any authentication/rate-limit considerations. For a read operation, this is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three short sentences. The first sentence is front-loaded with the primary purpose. The Returns section is slightly redundant given the output schema, but it does not hurt. Overall, it is efficiently written.

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, rich schema coverage, and an output schema, the description covers the essential purpose and return types. It does not explain domain-specific terms like 'VOC entries', but that is acceptable for a specialized tool. Complete for its complexity level.

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 tool has zero parameters, and the schema coverage is 100% trivially. According to guidelines, 0 parameters give a baseline of 4. The description adds no parameter info (none needed) and adequately describes the purpose without redundancy.

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 'Get information about the current Universe account' with a specific verb and resource. It lists the types of information returned (files, VOC entries, system info), distinguishing it from sibling tools like get_file_info or describe_file which target different resources.

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?

The description implies the tool is for retrieving account-level metadata, but it does not provide explicit guidance on when to use it versus alternatives like get_file_info or list_files. There are no usage restrictions or context cues.

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