Skip to main content
Glama

studio_discover_upstream

Reads tools and schemas from a locally configured upstream MCP so agents can inspect available capabilities without running paid generations.

Instructions

Read tools and schemas of a locally configured upstream MCP; does not run paid generations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "upstreamId": "<upstreamId>"
    },
    "name": "studio_discover_upstream"
  }
}

Input Schema

NameRequiredDescriptionDefault
upstreamIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/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 burden; it does disclose that the operation is a read and that it incurs no paid generation cost, which is meaningful behavioral context. It omits what happens on an unknown or unconfigured upstreamId, whether local configuration must pre-exist, and what the read returns.

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?

A single compact sentence with the core action front-loaded and the cost caveat appended; no wasted wording.

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 simple one-parameter read tool with no output schema, the description covers the action and the no-cost guarantee, but leaves the parameter and the failure/configuration preconditions unexplained. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter upstreamId, and the description adds no meaning about what an upstream ID is, where it comes from, or its format. The description does not compensate for the schema gap.

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?

States a specific verb (Read) and resource (tools and schemas of a locally configured upstream MCP), and adds a negative scope clause ('does not run paid generations') that separates it from generation/dispatch siblings. It stops short of naming an explicit alternative, so it is clear but not fully differentiated.

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?

The clause 'does not run paid generations' implies a when-not condition, useful for steering an agent away from paid execution paths. However, there is no positive statement of when to call this versus siblings like studio_preflight or studio_dispatch_job, so usage is only implied.

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