Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_project_info

Select an exact GPR project and optional environment settings to return its evaluated structure, creating a validated selection that later file tools reuse.

Instructions

Select an exact GPR project with an optional per-view environment and return its evaluated structure; later file tools reuse the validated selection

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": {
      "gpr_file": "<gpr_file>"
    },
    "name": "ada_project_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpr_fileYesAbsolute path to the .gpr project file
project_pathsNoOrdered absolute GPR search directories; when provided, replace the inherited GPR_PROJECT_PATH
scenario_variablesNoGPR scenario values which override configured defaults for this project view

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that selecting the project affects later tools and returns an "evaluated structure," but it omits failure behavior, selection persistence, validation errors, and what the evaluated structure contains.

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?

The description is a single front-loaded sentence with no wasted wording. It efficiently communicates the selection action, optional environment, return value, and downstream reuse.

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 stateful project-selection tool with no output schema and no annotations, the description should do more to explain the return shape, selection lifetime, and error behavior. It covers the core purpose and downstream reuse, but leaves important behavioral context unstated.

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 the input schema already explains all three parameters, including the absolute .gpr path, project search directories, and scenario variables. The description adds only framing such as "optional per-view environment" and "exact GPR project," which does not meaningfully extend parameter meaning beyond the schema.

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 specific verb and resource: "Select an exact GPR project" and "return its evaluated structure." It also notes that "later file tools reuse the validated selection," making the selection role clear, though it does not explicitly contrast with any sibling tool.

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 phrase "later file tools reuse the validated selection" implies this tool should be called before file-oriented tools, but it does not explicitly state when to call it, prerequisites, or when not to use it. Usage is implied rather than spelled out.

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