Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_graphql_audit

Assess a GraphQL endpoint via introspection evidence and enumerate query and mutation fields, persisting results without claiming vulnerabilities absent response evidence.

Instructions

Assess a GraphQL endpoint using introspection evidence and enumerate query/mutation fields. Results are persisted and do not claim vulnerabilities without response evidence.

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": {
      "engagement_id": "<engagement_id>",
      "url": "<url>"
    },
    "name": "oc_graphql_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
headersNo
timeoutNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, and idempotentHint=false. The description adds genuinely useful context beyond that: results are persisted, and it will not claim vulnerabilities without response evidence. It still omits what persistence means (where results land, whether they are overwritten) and any auth/rate-limit behavior for an open-world call.

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?

Two tight sentences with the core action front-loaded and the evidence caveat second. No filler, though the second sentence is slightly compressed to the point of ambiguity about what 'persisted' entails.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, for a four-parameter, open-world, non-idempotent tool, the definition leaves parameter meaning and invocation preconditions entirely unaddressed, which is a real gap.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description carries the full burden and fails to meet it. It says nothing about url, headers, timeout, or what engagement_id refers to or whether it must pre-exist.

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: 'Assess a GraphQL endpoint using introspection evidence and enumerate query/mutation fields.' That is concrete enough to distinguish it from a plain request-sending sibling like oc_graphql_request, though it never names the alternative explicitly.

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?

There is no when-to-use or when-not-to-use guidance. An agent cannot tell from the text whether this should be run before or instead of oc_graphql_request, or what preconditions (e.g., a reachable endpoint, an existing engagement) apply.

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