Skip to main content
Glama

Hot companies

sdr_company_heat

Read-only. Companies ranked by live signal heat, with ICP fit, signal types and contact status. One search (search_id, pages via offset up to any depth) or all searches merged (first 500 rows, offset + limit ≤ 500).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
search_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +500
    • addedInput schema / properties / offset
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / search_id
      Added value: +{
      +  "format": "uuid",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and delivers key details: it is read-only, describes pagination behavior per mode, and states the 500-row cap for merged searches with offset+limit ≤ 500. It does not cover auth needs or rate limits, but the core behavioral traits are disclosed.

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?

Two sentences, front-loaded with 'Read-only' and the core purpose, followed by a compact statement of the two query modes and pagination limits. Zero waste, efficient.

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?

Given no annotations, no output schema, and 3 parameters, the description adequately covers purpose, modes, and constraints for correct invocation. It lacks detail on return shape and the meaning of 'signal heat' ranking, but those are secondary for tool selection.

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 0%, so the description must compensate. It contextualizes all three parameters (search_id determines single-search mode; offset enables pagination; limit is capped in merged mode), but it omits defaults, format requirements (e.g., UUID), and the behavior when search_id is omitted (full merged mode). Partial compensation yields a 3.

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 resource (companies ranked by live signal heat) and enumerates returned fields (ICP fit, signal types, contact status), making the tool's function clear. It does not explicitly differentiate from siblings like sdr_company_detail or sdr_recent_signals, preventing a 5.

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 description implies usage for obtaining ranked hot companies and distinguishes two modes (single search vs all merged), but it provides no explicit guidance on when to choose this tool over alternatives or when not to use it.

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