Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

get_token_info

Retrieve metadata for the current API token, including scopes and owner details.

Instructions

Return metadata about the current API token (scopes, owner, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'get_token_info'. It is decorated with @mcp.tool(), making it an MCP tool. It calls the Humaans API endpoint /token-info via the HTTP client and returns the response.
    @mcp.tool()
    async def get_token_info() -> dict[str, Any]:
        """Return metadata about the current API token (scopes, owner, etc.)."""
        return await client().get("/token-info")
  • The tool is registered via the @mcp.tool() decorator from FastMCP on the 'mcp' instance defined on line 7 (mcp = FastMCP('humaans')).
    @mcp.tool()
    async def get_me() -> dict[str, Any]:
        """Return the authenticated user for the current API token."""
        return await client().get("/me")
    
    
    @mcp.tool()
  • The client().get() method used by the handler to make the HTTP GET request to the Humaans API.
    async def get(self, path: str, params: dict[str, Any] | None = None) -> Any:
        clean = {k: v for k, v in (params or {}).items() if v is not None}
        resp = await self._client.get(path, params=clean)
        if resp.status_code >= 400:
            try:
                body = resp.json()
            except Exception:
                body = resp.text
            raise HumaansError(resp.status_code, path, body)
        return resp.json()
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns metadata (scopes, owner), which is helpful, but does not mention potential side effects (none expected), rate limits, or authentication requirements. Acceptable for a read operation.

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?

Single sentence, under 20 words, with no redundancy. Every word adds value. Excellent conciseness and structure.

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 zero parameters and the presence of an output schema (which presumably details the metadata fields), the description is sufficient. It gives a high-level overview (scopes, owner, etc.) and the output schema fills in details. No gaps identified.

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?

Input schema is empty with 100% trivial coverage. Baseline is 3. Description adds no parameter info, but clarifies the subject is the 'current API token', providing context beyond the schema. No parameters exist, so the score is appropriate.

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 tool returns metadata about the current API token, using specific verb ('return') and resource ('metadata about the current API token'). This distinguishes it from sibling tools that focus on people, companies, or reports.

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 usage context (when token info is needed) but provides no explicit guidance on when not to use or alternatives. For a simple read-only tool, this is adequate but lacks depth.

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/ptorsten/humaans-mcp'

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