Skip to main content
Glama
yeison-liscano

Simple HTTP MCP Server

Get Called Tools

get_called_tools
Idempotent

Retrieve a list of Python functions executed on the Simple HTTP MCP Server via its JSON-RPC interface to monitor activity and manage tool usage.

Instructions

Get the list of called tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
called_toolsYesThe list of called tools

Implementation Reference

  • The async handler function that executes the get_called_tools tool logic, retrieving called tools from context.
    async def get_called_tools(
        args: Arguments[GetCalledToolsInput],
    ) -> GetCalledToolsOutput:
        """Get the list of called tools."""
        context = args.get_state_key("context", Context)
        return GetCalledToolsOutput(called_tools=context.get_called_tools())
  • Pydantic models defining input (empty) and output schema for get_called_tools tool.
    class GetCalledToolsInput(BaseModel):
        pass
    
    
    class GetCalledToolsOutput(BaseModel):
        called_tools: list[str] = Field(description="The list of called tools")
  • Registration of the get_called_tools tool in the TOOLS tuple.
    Tool(
        func=get_called_tools,
        inputs=GetCalledToolsInput,
        output=GetCalledToolsOutput,
    ),
  • Helper method on Context class that returns the list of called tools.
    def get_called_tools(self) -> list[str]:
        return self.called_tools
Behavior4/5

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

The description doesn't add behavioral details beyond what annotations provide, but annotations are comprehensive (readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false). Since annotations cover key behavioral traits, the description doesn't need to compensate, and there's no contradiction with annotations.

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 with no wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 0 parameters, comprehensive annotations, and an output schema, the description is complete enough for its purpose. It could be slightly improved by clarifying what 'called tools' means, but the structured data compensates well.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate, earning a baseline score for this scenario.

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

Purpose3/5

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

The description 'Get the list of called tools' clearly states the action (get) and resource (called tools), but it's somewhat vague about what 'called tools' means in this context. It doesn't differentiate from sibling tools like 'get_time' or 'get_weather' beyond the resource name.

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 context, prerequisites, or comparisons with sibling tools like 'tool_that_access_request' that might serve similar purposes.

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/yeison-liscano/http_mcp'

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