Skip to main content
Glama

The Revenue AI Report

Get AI tool profile

get_tool
Read-onlyIdempotent

Get one vendor profile in full from The Revenue AI Report AI tool library, by slug or by name. Returns the directory record plus the depth layer: why the adoption effort level is what it is, owning seat and journey stage, buy checks, published case studies, documented discrepancies between vendor claim and independent reporting, corporate status changes, and any Reversal Ledger record naming this vendor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTool name, used when the slug is unknown.
slugNoTool slug, e.g. clari.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
faqsYes
toolYes
adoptionYes
evidenceYes
buyChecksYes
placementYes
relatedSkillsYes
reversalLedgerYes
corporateStatusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "adoption": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "level": {
      +          "type": "number"
      +        },
      +        "meaning": {
      +          "type": "string"
      +        },
      +        "rationale": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "level",
      +        "meaning",
      +        "rationale"
      +      ],
      +      "type": "object"
      +    },
      +    "buyChecks": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "corporateStatus": {},
      +    "evidence": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "caseStudies": {
      +          "items": {
      +            "additionalProperties": {},
      +            "properties": {
      +              "customer": {
      +                "type": "string"
      +              },
      +              "outcome": {
      +                "type": "string"
      +              },
      +              "url": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "customer",
      +              "outcome",
      +              "url"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "claimAudits": {
      +          "items": {
      +            "additionalProperties": {},
      +            "properties": {
      +              "claim": {
      +                "type": "string"
      +              },
      +              "counter": {
      +                "type": "string"
      +              },
      +              "source": {
      +                "type": "string"
      +              },
      +              "url": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "claim",
      +              "counter",
      +              "source",
      +              "url"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "fieldNote": {},
      +        "status": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "status",
      +        "caseStudies",
      +        "claimAudits",
      +        "fieldNote"
      +      ],
      +      "type": "object"
      +    },
      +    "faqs": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "a": {
      +            "type": "string"
      +          },
      +          "q": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "q",
      +          "a"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "placement": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "oar": {
      +          "type": "string"
      +        },
      +        "seat": {
      +          "type": "string"
      +        },
      +        "stage": {
      +          "type": "string"
      +        },
      +        "teams": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "stage",
      +        "oar",
      +        "seat",
      +        "teams"
      +      ],
      +      "type": "object"
      +    },
      +    "relatedSkills": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "skillFileUrl": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "name",
      +          "url",
      +          "skillFileUrl"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "reversalLedger": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "company": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "company",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "tool": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "category": {
      +          "type": "string"
      +        },
      +        "description": {
      +          "type": "string"
      +        },
      +        "functions": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "maturity": {
      +          "type": "number"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "slug": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        },
      +        "website": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "slug",
      +        "name",
      +        "category",
      +        "description",
      +        "functions",
      +        "maturity",
      +        "website",
      +        "url"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "tool",
      +    "placement",
      +    "adoption",
      +    "evidence",
      +    "corporateStatus",
      +    "reversalLedger",
      +    "buyChecks",
      +    "relatedSkills",
      +    "faqs"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds substantial value by detailing exactly what the depth layer includes (adoption effort rationale, owning seat, buy checks, case studies, discrepancies, corporate changes, Reversal Ledger records). This goes beyond the annotations and clarifies the return content, though it does not describe error handling or absence cases.

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 description is a single, information-dense sentence. It front-loads the core action and then lists the detailed contents efficiently. There is no filler, though the list of depth-layer items is lengthy; each item earns its place by informing the agent of what to expect.

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 the tool has two optional parameters, an output schema, and annotations covering safety, the description is largely complete. It explains the selection method and the full scope of returned data. It does not mention authentication prerequisites or error responses, but these are not typically required for a read-only lookup tool, and the output schema covers return structure.

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 100%, so both name and slug are already documented individually. The description simply restates that selection is 'by slug or by name', which adds no new semantic information. It does clarify that only one of the two is needed, but that is also implied by the schema's 'used when the slug is unknown' note.

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 states a specific verb (get), a specific resource (one vendor profile), and the selection method (by slug or by name). It also enumerates the exact contents of the returned record, making it unmistakably distinct from the many sibling get_* tools which target different resource types.

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 this is for retrieving a specific known tool by slug or name, and the sibling list includes search_tools and list_tools for discovery. However, it does not explicitly state when to prefer this tool over alternatives or provide exclusion conditions. Usage context is implied but not spelled out.

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