Skip to main content
Glama
sitbon

Magg

by sitbon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

proxy

Access and manage mounted MCP servers through a unified interface. List, inspect, or call tools, resources, and prompts across servers.

Instructions

Main proxy tool for dynamic access to mounted MCP servers.

This tool provides a unified interface for:

  • Listing available tools, resources, or prompts across servers

  • Getting detailed info about specific capabilities

  • Calling tools, reading resources, or getting prompts

Annotations are used to provide rich type information for results, which can generally be expected to ultimately include JSON-encoded EmbeddedResource results that can be interpreted by the client.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments for a 'call' action (call tool, read resource, or get prompt). Can be a dict or JSON string.
pathNoName or URI of the specific tool/resource/prompt (with FastMCP prefixing). Required for 'info' and 'call' actions; not allowed for 'list'.
typeYesType of MCP capability to interact with: tool, resource, or prompt.
limitNoMaximum number of items to return (for 'list' action only). Default: 100
actionYesAction to perform: list, info, or call.
offsetNoNumber of items to skip (for 'list' action only). Default: 0
filter_serverNoFilter results by server name prefix (for 'list' action only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / path / description
      Previous value: -"Name or URI of the specific tool/resource/prompt (with FastMCP prefixing).\nNot allowed for 'list' and 'info' actions."New value: +"Name or URI of the specific tool/resource/prompt (with FastMCP prefixing).\nRequired for 'info' and 'call' actions; not allowed for 'list'."
  2. Changed8 schema fields changedv1.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / action / title
      Removed value: -"Action"
    • removedInput schema / properties / args / title
      Removed value: -"Args"
    • removedInput schema / properties / filter_server / title
      Removed value: -"Filter Server"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • removedInput schema / properties / type / title
      Removed value: -"Type"
  3. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It adds useful context about the return shape (JSON-encoded EmbeddedResource results interpretable by the client), but says nothing about whether 'call' mutates state, permission/auth requirements, or error behavior. The output-format note is real added value, but the side-effect profile of invoking arbitrary remote tools is undisclosed.

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?

Front-loaded with the core role, then a tight three-bullet breakdown of actions and a closing note on results. Every sentence is functional, though the final sentence about annotations is slightly abstract and ordered behind the action list.

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?

For a 7-parameter meta-tool with no annotations and no output schema, the description covers the action space but leaves the parameters' interaction (e.g., how path/args relate to each action) and the effect of 'call' to the schema alone. It is minimally viable but not complete for a tool that can invoke arbitrary remote capabilities.

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?

Schema description coverage is 100%, so all seven parameters are already documented in the schema (args, path, type, limit, offset, filter_server, action). The description names the three actions but adds no syntax, format, or cross-parameter constraints beyond the schema, so the baseline of 3 is appropriate.

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 states a clear role (a proxy into mounted MCP servers) and enumerates the three action families (list/info/call) that match the 'action' enum, so an agent can tell it is the runtime access path rather than the magg_* server-management siblings. It stops short of explicitly contrasting itself with those siblings, but the purpose is unambiguous.

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?

Usage is only implied by the bullet breakdown of list/info/call; there is no explicit statement of when to reach for this proxy versus the magg_* management tools, and no prerequisites or exclusions. An agent can infer the action mapping but gets no routing guidance.

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

Deploy Server

Other Tools