Skip to main content
Glama

Inspect dynamic hosting requirements

runtime_contract
Read-onlyIdempotent

Reports currently supported Node.js, PHP and Python runtimes, dependencies, persistent storage, managed services, workers, scheduled tasks and packaging requirements. Project subdomains are optional.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "runtime_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idNoWorkspace to inspect or create in. Omit or pass null for Personal. Selection applies only to this call; workspace usage is billed to its owner.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the data is "currently supported," hinting the values are time-sensitive, but it never says whether the report is static reference data or scoped to the given workspace, nor what shape the response takes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single long sentence is front-loaded with the useful content, but the trailing "Project subdomains are optional" is contextually orphaned — it is unclear whether it refers to hosting requirements, to this call's arguments, or to a separate setup step. That sentence does not earn its place without elaboration.

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?

With no output schema, the description partially compensates by enumerating the categories of information reported, which is genuinely useful. But it leaves unresolved whether the output is workspace-specific or generic documentation, and the dangling subdomain remark adds ambiguity rather than clarity for a tool this simple.

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% and the single workspace_id parameter is fully documented in the schema, including the Personal-default behaviour and the no-inference warning. The description contributes nothing about the parameter, so the baseline of 3 applies.

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 ("Reports") and enumerates the resource set: supported Node.js/PHP/Python runtimes, dependencies, storage, managed services, workers, scheduled tasks, packaging. An agent knows this is an informational lookup, not a mutation. It does not, however, distinguish itself from siblings like configure_dynamic_project or create_dynamic_project, where similar runtime information might surface.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The only quasi-guidance is the trailing "Project subdomains are optional," which is a fact about the report contents rather than a routing hint. An agent must infer that this is a pre-configuration reference call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources