Skip to main content
Glama
Sign In
NeuralVerge

NeuralVerge

Official
by neuralverge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

run_gartner_vendor

Fetch a Gartner Peer Insights vendor profile by alias or URL to get markets, products, and ratings.

Instructions

Get a Gartner Peer Insights vendor profile by alias or URL: markets, products, and ratings. Flat 5 points per successful run.

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": {
      "vendor": "<vendor>"
    },
    "name": "run_gartner_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorYesVendor alias or URL. e.g. forcepoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It usefully discloses a flat 5-point cost per successful run, but does not describe authentication needs, rate limits, failure behavior, or whether the operation is read-only beyond the implication of 'Get'.

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 two tight sentences: the first front-loads purpose and scope, and the second adds cost information. There is no wasted text.

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 simple one-parameter lookup with no output schema, the description covers the core purpose, input form, included data categories, and cost. It does not fully document response structure or error behavior, but the essentials are present.

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%, and the single parameter is fully documented in the schema with an example. The description repeats that the vendor can be an alias or URL but adds no further meaning beyond the schema.

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

Purpose4/5

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

The description states a specific verb and resource: 'Get a Gartner Peer Insights vendor profile by alias or URL,' and lists the included data types (markets, products, ratings). It is clear what the tool does, but it does not explicitly differentiate itself from adjacent Gartner tools such as run_gartner_product or run_gartner_market.

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 description gives no guidance on when to use this tool versus alternatives. It does not mention sibling tools, prerequisites, or selection criteria beyond the input being an alias or URL.

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

Deploy Server

Other Tools