Skip to main content
Glama

getShotData

Retrieve detailed espresso shot data by ID from Gaggiuino MCP Server, enabling analysis and insights directly from the machine controller.

Instructions

Get espresso shot data for an id.

Args:
    id: Shot id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler function for the 'getShotData' tool. It is decorated with @mcp.tool() for registration. Fetches shot data from the Gaggiuino API endpoint, handles errors, formats the data using format_shot, and returns it as a JSON string.
    @mcp.tool()
    async def getShotData(id: str) -> str:
        """Get espresso shot data for an id.
    
        Args:
            id: Shot id
        """
        url = f"{API_BASE}/api/shots/{id}"
        data = await make_gg_request(url)
    
        if not data:
            return "Unable to fetch shot or no shot found."
    
        shot = format_shot(data)
        return shot
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'Get' which implies a read operation, but doesn't disclose behavioral traits such as error handling, data format, permissions needed, or rate limits. This is a significant gap for a tool with no annotation coverage.

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 brief and front-loaded with the main purpose, followed by a parameter explanation. It avoids unnecessary words, but the structure could be improved by integrating the parameter info more seamlessly or adding context in a single coherent sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on return values, error cases, or how it interacts with sibling tools. For a tool with one parameter but undefined behavior, this is inadequate.

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?

The schema description coverage is 0%, but the description adds meaning by specifying that 'id' is a 'Shot id'. This clarifies the parameter's purpose beyond the schema's basic type. However, it doesn't detail format, constraints, or examples, so it only partially compensates for the low coverage.

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 action ('Get espresso shot data') and the resource ('for an id'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'getLatestShotId' or 'getStatus', which might retrieve related data, so it doesn't reach the highest score.

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?

No guidance is provided on when to use this tool versus alternatives like 'getLatestShotId' or 'getStatus'. The description only states what it does, without context on prerequisites, scenarios, or exclusions, leaving the agent to infer usage.

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

Related 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/AndrewKlement/gaggiuino-mcp'

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