Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

find_company_insights

Read-only

Browse profiled companies (Fortune 1000) by name or industry; ranked by overall technology-readiness signal. industry takes an insights industry NAME from insights_industries (e.g. "Industrial") — a different vocabulary from the catalog industry slugs find_providers uses — and matches every roster a company sits on, not just its primary. Understanding plan. Priced per result — $0.005 per request plus $0.0002 per record returned (less past 100), capped at $0.50 a request, under pay-as-you-go; included in Understanding and Influence. Estimate first at /api/v1/prices/estimate. See apis://prices.

Input Schema

NameRequiredDescriptionDefault
qNoFree text matched against company name, e.g. "stripe".
pageNoPage number, 1-based (default 1).
limitNoResults per page, 1-100 (default 25).
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
industryNoIndustry slug to narrow to, e.g. "artificial-intelligence".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 1-based (default 1). Use with `limit` to walk a long list."New value: +"Page number, 1-based (default 1)."
  2. Changed4 schema fields changed
    • addedInput schema / properties / industry / description
      Added value: +"Industry slug to narrow to, e.g. \"artificial-intelligence\"."
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
    • addedInput schema / properties / q / description
      Added value: +"Free text matched against company name, e.g. \"stripe\"."
  3. Changed1 schema field changed
    • addedInput schema / properties / industry
      Added value: +{
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: ranking behavior, per-record/per-request pricing with a cap, plan gating, and an estimate endpoint. It does not describe pagination behavior or return shape, but the pricing/plan detail is substantive.

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?

The core purpose and the industry-vocabulary caveat are front-loaded before pricing detail. The pricing sentence is long and slightly crammed, but each clause carries distinct operational information (rate, cap, plan inclusion, estimate path), so it largely earns its space.

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?

For a read-only, no-output-schema discovery tool, the description covers purpose, ranking, parameter vocabulary, plan gating, and cost. The only notable gap is the relationship to get_company_insight and return/pagination shape, which is minor here.

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?

Schema coverage is 100%, so the baseline is 3. The description goes further by explaining that `industry` takes an insights industry NAME from insights_industries rather than a catalog slug, and that it matches every roster a company sits on. This is valuable disambiguation, though it sits in tension with the schema's own example ("artificial-intelligence"), which is itself described as a slug.

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

Purpose5/5

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

States a specific verb (browse/find) and resource (profiled Fortune 1000 companies), plus the ranking signal (technology-readiness). It explicitly distinguishes its industry vocabulary from find_providers, so an agent can separate it from the catalog-side sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear routing context: the industry parameter uses a different vocabulary than find_providers, and it notes the Understanding plan requirement. It does not address when to use this list tool vs the singular get_company_insight sibling, leaving that inference to the agent.

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

All apis-io toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources