Skip to main content
Glama

Inspect dynamic project

get_dynamic_project
Read-onlyIdempotent

Returns an authorized application project’s runtime configuration, deployment events, masked variable names, domains, schedules, usage and backup availability.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_dynamic_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral notes beyond that: results are scoped to an *authorized* project, and variable names are returned *masked*. It stops short of saying anything about error behavior or result size/pagination.

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?

A single front-loaded sentence with the resource and scope stated first, followed by the payload enumeration; no filler or hedging. The long trailing list is dense but every item contributes to distinguishing the tool's output.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so by enumerating the returned facets. For a single-parameter, read-only inspection tool that is largely sufficient; only the lack of sibling differentiation and error/limit context keeps it from being complete.

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 project_id parameter is already fully documented in the schema, including the resolve-first instruction and the pattern. The description adds no information about the parameter, so the baseline 3 is the ceiling here.

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 ("Returns") and a specific resource (an authorized application project's runtime configuration) and enumerates the payload facets — deployment events, masked variable names, domains, schedules, usage, backup availability. That enumeration meaningfully separates it from narrower siblings like get_project_security or get_deployment_status, though the description never explicitly names a contrast.

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 alternative is named despite close siblings such as get_project, get_project_security, and get_deployment_status. The agent must infer the selection rule entirely from the word "dynamic" and the enumerated contents.

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