Skip to main content
Glama

Run a cve.now operation

execute

Run one operation by its id from search, with the arguments its input schema describes, for example {"name":"entities.get","arguments":{"id":"CVE-2021-44228"}}. The answer is the operation's JSON, the same as its REST twin. Unknown or misplaced arguments are refused with the ones that are valid.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe operation id from search, such as entities.get.
argumentsNoArguments matching the operation's inputSchema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The operation id from search, such as cve.get."New value: +"The operation id from search, such as entities.get."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description still adds real behavioral value: the response is the operation's raw JSON matching its REST twin, and invalid or misplaced arguments are refused with the list of valid ones — an error contract an agent needs. It omits any warning that some operations may have side effects.

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?

Three short sentences, front-loaded with the core action and followed by an example, return behavior, and error behavior — no padding. The 'REST twin' reference is mild jargon that assumes external context.

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 generic dispatcher with a nested arguments object and no output schema, the description covers the input shape, where the operation id comes from, what comes back, and how errors surface. What's missing is any indication that dispatched operations vary in effect, including ones that write.

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 coverage is 100%, so both parameters are already documented in the schema, including that 'arguments' must match the operation's inputSchema. The description reinforces this with a concrete example but adds no new semantic constraint beyond what the schema states.

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 and mechanism: run one operation by its id, where the id comes from search. This cleanly separates it from the sibling 'search' (discovery) and an agent can tell which of the two to call without inspecting either 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?

The phrase 'by its id from search' establishes the prerequisite workflow — discover first, then execute — and the inline example shows the exact call shape. It does not spell out when-not-to-use or how to handle operations that mutate state, so it stops short of a full routing guide.

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