Skip to main content
Glama

Company search

companies_search
Read-only

Company search (GET https://app.deepvalues.ai/api/v1/companies — 0.001 credits per call ($0.005 when paid per call over x402); works with no credentials up to 25 call(s)/day per address) Missing data? Call request_data.

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

Input Schema

NameRequiredDescriptionDefault
qNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the cost model (0.001 credits per call, $0.005 under x402) and the credential-free rate limit of 25 calls/day per address are genuine additions an agent needs before invoking it. It does not describe the response payload or pagination behavior, which is why this stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, and the cost/auth information is worth the space. However, it is structured as one dense parenthetical that leads with a tautology and buries the operationally important rate limit mid-clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and zero parameter documentation, the description carries the burden for query semantics and return shape and delivers neither. Pricing and auth are covered well, but an agent still cannot form a correct query from this definition alone.

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

Parameters2/5

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

Schema description coverage is 0% and the description says nothing about either parameter. The critical unknown — what `q` matches on and whether `limit` caps results or pages them — is left entirely undocumented in both structured fields and prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description text is literally "Company search", which restates the tool name and title without adding a verb-resource distinction or saying what is actually searched over (names, tickers, domains). The remainder of the sentence is endpoint/pricing detail, not purpose. An agent cannot tell from this why it should pick companies_search over company_overview.

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?

The only routing hint is "Missing data? Call `request_data`", which describes a fallback rather than when to use this tool versus siblings like company_overview or filings. There is no statement of what queries this endpoint is appropriate for, nor any exclusion.

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