Skip to main content
Glama

get_deal_os_overview

Read-onlyIdempotent

What Deal OS is, who it is for, and the list of its public pages. Ends with the source URL.

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": "get_deal_os_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description's only genuine addition beyond that structured data is that the response ends with the source URL, which hints at citation-friendly output. It says nothing about size, truncation, or freshness of the overview content.

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 short sentence that front-loads the content scope and appends the output detail at the end. Nothing is redundant, though it is arguably over-compressed — a noun phrase rather than a full clause, which costs some clarity.

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?

This is a simple, zero-argument read tool with an output schema and full annotation coverage, so the description needn't explain return values or safety. Listing the three content sections is sufficient to set expectations. The remaining gap is guidance on when an agent should reach for this versus the other Deal OS reference tools.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter semantics to explain or omit. The description correctly does not waste words on arguments.

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 names the resource ('Deal OS overview') and enumerates its three content components: what Deal OS is, who it is for, and its public pages, plus a trailing source URL. An agent can tell this is a static reference/overview lookup rather than a search or pricing call. It stops short of an explicit verb and never differentiates itself from siblings like get_deal_os_pricing, leaving the differentiation implicit.

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 statement, no exclusion, and no mention of any alternative tool. The agent must infer from the content name alone that this is the introductory/contextual call rather than one of the checklist, pricing, or buyer-answer siblings. No prerequisites or typical ordering are given.

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