get_testing_settingsRead the project's testing settings. schemaNullMode decides how contract assertions treat null values against a schema. Requires project context.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly says 'Read', which aligns perfectly with the readOnlyHint annotation, ensuring no contradiction. It also mentions the requirement for project context, which is a behavioral prerequisite. No side effects are implied, and the description is transparent about the operation being read-only.
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 concise, consisting of two sentences that deliver the core purpose and a relevant detail. It avoids unnecessary verbiage and is well-structured, with the main action stated first. The additional sentence about schemaNullMode adds value without excessive length.
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?
The description is complete for its simplicity: it states what the tool does, a key setting it covers, and a prerequisite (project context). Since there is no output schema, no return value documentation is needed. The description fully equips an agent to decide when and how to use this tool.
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 tool has no parameters, so there is no parameter semantics to explain. The description mentions schemaNullMode as a setting, not a parameter, which is appropriate. The baseline for zero parameters is 4, and the description does not introduce any confusion about parameters.
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 reads the project's testing settings, which is a specific and unambiguous action. It also mentions schemaNullMode, a key setting, further clarifying its purpose. This distinguishes it from other get_* tools that retrieve test results, runs, or suites.
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 notes that it requires project context, which is a useful prerequisite. While it doesn't explicitly mention alternatives or when not to use it, the name and description make its intended use clear. The context requirement is a concrete guideline for when this tool can be invoked.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tools are mostly distinct with clear descriptions. Some pairs like get_header_policies vs get_resolved_headers or get_environment_verification vs get_monitoring_sync_status could be slightly confusing, but the descriptions clarify scope and purpose.
All tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, update_, manage_, etc.). Even the few bare verbs like 'search' and 'set_context' are consistent with the naming scheme.
With 165 tools, the server is extremely heavy. This far exceeds the 'too many' threshold of 25+, making it difficult for an agent to navigate and select the right tool efficiently.
The tool surface covers a very broad API lifecycle domain: specs, environments, test cases, monitors, mock servers, security, governance, documentation, and team management. Read and write operations are present across most areas, with no obvious missing core functionality.