Skip to main content
Glama
hofill
by hofill

session_info

Retrieve active client session details, including optional authentication token, for managing HTTP requests and DNS configurations in RequestRepo.

Instructions

Return session info for the active requestrepo client.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The session_info handler method in RequestrepoMCPService class that implements the actual business logic. Returns session info including subdomain, domain, endpoint, and optionally the token based on the include_token parameter.
    def session_info(self, *, include_token: bool = False) -> dict[str, Any]:
        client = self._client()
        payload: dict[str, Any] = {
            "subdomain": client.subdomain,
            "domain": client.domain,
            "endpoint": f"{client.subdomain}.{client.domain}",
        }
        if include_token:
            payload["token"] = client.token
        return payload
  • Registration of the session_info tool using the @mcp.tool() decorator. This defines the MCP tool interface that accepts an optional include_token parameter and delegates to the service's session_info method.
    @mcp.tool()
    def session_info(include_token: bool = False) -> dict[str, Any]:
        """Return session info for the active requestrepo client."""
        return resolved_service.session_info(include_token=include_token)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Return'), but doesn't mention authentication requirements, rate limits, error conditions, or what constitutes 'session info' (e.g., user identity, permissions, expiration). The description is minimal and lacks important behavioral context.

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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

Given the tool's simplicity (one optional parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and a vague 'session info' concept, it lacks important context about what information is returned and under what conditions. The output schema existence prevents a lower score.

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 description mentions no parameters, while the schema has one parameter with 0% description coverage. Since there are zero parameters documented in the description, this meets the baseline of 4 for having no parameters to explain. The description doesn't need to compensate for schema gaps because it doesn't reference parameters at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Return') and resource ('session info'), and specifies the scope ('for the active requestrepo client'). It doesn't explicitly differentiate from sibling tools, but the purpose is unambiguous within this context.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, typical use cases, or comparison with sibling tools that might also provide session-related information (though none are obviously named as such).

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/hofill/RequestRepo-MCP'

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