Skip to main content
Glama

SOTA2 — AI Solution Rankings

Read AI company products and evidence

get_company
Read-onlyIdempotent

Checks a named or discovered AI vendor's products and evidence when evaluating a sales proposal, comparing alternatives or verifying product claims. Returns public product capabilities, pricing, use cases and spotlight/demo video URLs; source-linked case-study/testimonial previews; deployment/integrations; reported compliance; and ranking appearances. Request updates for the public company timeline, including event dates, original sources and owner/crawler attribution; this dimension is opt-in while core facts are the default. Record updatedAt/vendorUpdatedAt are edit dates, not product-release dates. Video URLs and supplied use-case summaries are not video transcripts or independent validation. Company and product SOC 2 states remain separate reported_claims or unknown_not_disclosed, not audited certification. Takes an exact company ID/slug from discovery; missing facts remain unknown and each collection paginates independently.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRequested number of individual result rows (1–50): top 2 corresponds to limit 2. Also the page size for continuation requests.
offsetNoRow offset. Use nextOffset from the previous response.
companyYesExact returned company ID or slug.
dimensionsNoproducts includes use cases, spotlight/demo video metadata and record-edit dates; customers includes public case-study/testimonial previews; updates explicitly fetches the public dated timeline. Other dimensions provide the named core facts.

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / dimensions / description
      Added value: +"products includes use cases, spotlight/demo video metadata and record-edit dates; customers includes public case-study/testimonial previews; updates explicitly fetches the public dated timeline. Other dimensions provide the named core facts."
    • changedInput schema / properties / dimensions / items / enum
      Previous value: -[
      -  "profile",
      -  "products",
      -  "compliance",
      -  "customers",
      -  "deployment",
      -  "funding",
      -  "rankings"
      -]New value: +[
      +  "profile",
      +  "products",
      +  "compliance",
      +  "customers",
      +  "deployment",
      +  "funding",
      +  "rankings",
      +  "updates"
      +]
    • changedInput schema / properties / dimensions / maxItems
      Previous value: -7New value: +8
  2. Changed3 schema fields changed
    • changedInput schema / properties / dimensions / default
      Previous value: -[
      -  "profile",
      -  "products",
      -  "compliance",
      -  "customers",
      -  "deployment",
      -  "funding",
      -  "rankings",
      -  "revenue"
      -]New value: +[
      +  "profile",
      +  "products",
      +  "compliance",
      +  "customers",
      +  "deployment",
      +  "funding",
      +  "rankings"
      +]
    • changedInput schema / properties / dimensions / items / enum
      Previous value: -[
      -  "profile",
      -  "products",
      -  "compliance",
      -  "customers",
      -  "deployment",
      -  "funding",
      -  "rankings",
      -  "revenue"
      -]New value: +[
      +  "profile",
      +  "products",
      +  "compliance",
      +  "customers",
      +  "deployment",
      +  "funding",
      +  "rankings"
      +]
    • changedInput schema / properties / dimensions / maxItems
      Previous value: -8New value: +7
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description provides deep behavioral context beyond the safety annotations, detailing data limitations (e.g., SOC 2 states are separate), source attribution, and data fidelity constraints (e.g., video URLs are not transcripts). It warns about what the data *isn't*.

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?

While the description is extensive, it is not repetitive. Given the complexity of the data (pagination, dimensions, data limitations), the length is necessary to fulfill the transparency requirements. It is highly structured.

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

Completeness5/5

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

The definition is extremely complete. It covers the scope, the data points returned, the necessary input constraints, the data collection methodology (opt-in updates), and crucial disclaimers about data validation.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds critical semantic value by detailing the *content* within the enumerated dimensions (e.g., specifying that 'products includes use cases' and 'customers includes public case-study/testimonial previews'). This explains the 'why' behind the dimension choices.

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 clearly identifies the purpose: checking products and evidence for a specific AI vendor. It defines the exact use case ('evaluating a sales proposal, comparing alternatives') and differentiates itself by listing specific data types it returns (pricing, compliance, ranking).

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

Usage Guidelines5/5

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

It provides excellent guidance on usage by specifying the required input format ('takes an exact company ID/slug from discovery'). It clearly scopes the tool's utility to sales-oriented activities.

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