gosce-portfolio-router
Server Details
Single entry point for the GOSCE portfolio: routes orchestrators to verified agents by capability, w
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.7/5 across 1 of 1 tools scored.
With only a single tool, there is no possibility of confusion between tools. The tool is uniquely named and serves a clear purpose.
The single tool name 'invoke' is a verb, which is consistent and clear. There are no other tools to create inconsistency.
A single tool is too few for typical MCP servers, as it limits the server's functionality to one operation. While the tool may be sufficient for a simple router, the count feels thin and underdeveloped for most use cases.
The server's single tool covers the core routing operation, but lacks any auxiliary tools for listing capabilities, managing agents, or retrieving metadata. This leaves notable gaps for agents that might need to discover or configure the routing logic.
Available Tools
1 toolinvokeAInspect
Single entry point for the GOSCE portfolio: routes orchestrators to verified agents by capability, with real example output from the router's own /selftest probes (a quality-assured broker, not a directory).
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | JSON request for this capability (the same body you'd send as an A2A message). |
Tool Definition Quality
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 adds behavioral context by stating the tool is a 'quality-assured broker, not a directory' and mentions providing 'real example output from the router's own /selftest probes.' This goes beyond a simple invocation description but does not disclose side effects, failure modes, or authentication requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that efficiently conveys the tool's role and key characteristics. It is front-loaded with 'Single entry point' and includes specific qualifiers. However, the dense phrasing could be slightly restructured for improved readability without losing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple routing tool with one parameter and no output schema, the description provides essential context (broker vs. directory, self-test examples). However, it omits details about error handling, rate limits, and the structure of the returned output (the mention of 'example output' is vague). The description is sufficient but not comprehensive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'input' has 100% schema description coverage. The description adds value by explaining it is 'the same body you'd send as an A2A message,' providing concrete context beyond the schema's generic 'JSON request.' This fully clarifies the parameter's purpose and format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose as a single entry point that routes orchestrators to verified agents by capability. The verb 'routes' and specific resource 'orchestrators to agents' provide clear action and target. However, the phrasing ('GOSCE portfolio', 'quality-assured broker') is somewhat abstract and could be more concrete for an AI agent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage as a singular entry point ('Single entry point'), suggesting it is the primary or only tool for routing. However, it lacks explicit guidance on when to use this tool versus alternatives or when not to use it. With no sibling tools listed, the context is minimal but acceptable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!