Skip to main content
Glama
Sign In

api-evangelist

by com.apievangelist
OverviewDiscussionsAdmin

find_company_insights

Read-only

Browse profiled companies (Fortune 1000 + API providers) by name; ranked by technology-readiness signal. Free.

Input Schema

NameRequiredDescriptionDefault
qNoFree text matched against company name, e.g. "chase".
pageNoPage number, 1-based (default 1). Use with `limit` to walk a long list.
limitNoResults per page, 1-100 (default 25).
contextNoOptional: 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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. \"chase\"."
  2. 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"
+}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the 'readOnlyHint' annotation, the description adds valuable behavioral context: the tool operates on a specific, curated subset of data (Fortune 1000 + API providers) and includes the ranking criteria ('ranked by technology-readiness signal').

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?

The description is highly concise, fitting all necessary information (action, resource, scope, ranking, cost) into a single, efficient sentence without waste.

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?

The description clearly establishes the identity of the profiled companies and the mechanism by which they are presented (ranking/browsing). Given that the schema handles pagination and the annotations handle safety, the description is complete enough for the agent to confidently invoke the tool.

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?

Since the schema description coverage is 100%, the schema already provides detailed definitions for all parameters, including `q`. The description does not add unique semantic meaning beyond what the structured schema provides, making baseline 3 appropriate.

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?

The description uses the specific verb 'Browse' and defines the resource scope clearly ('profiled companies (Fortune 1000 + API providers)'). It also specifies the key sorting mechanism ('ranked by technology-readiness signal').

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?

The description defines the specific population being browsed (Fortune 1000 + API providers), giving a clear boundary for usage. While it doesn't explicitly name the alternative tool, the use of 'Browse' implies a list/search operation distinct from a single 'Get' operation.

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

All api-evangelist 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