Skip to main content
Glama

BRAINIAC GraphQL Federation Security

Score field authorization coverage

graphql-security_field-authorization-coverage

Count object and interface fields in the supplied subgraph SDL and mark a field when its line, or its type line, contains one of the supplied directive names. Coverage is the share of marked fields. This is a text count. It does not compose a supergraph or decide whether a request would be allowed. Price $0.04 USDC. POST /api/v1/graphql-security/field-authorization-coverage. Unpaid calls return 402 and do not 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": {
      "protected_directives": "<protected_directives>",
      "subgraphs": "<subgraphs>"
    },
    "name": "graphql-security_field-authorization-coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
subgraphsYes
protected_directivesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations the description must carry the full behavioral burden, and it does disclose meaningful operational facts: the tool performs a textual count rather than semantic composition, unpaid calls return 402 and do not execute, and the cost is $0.04 USDC via a POST endpoint. It does not describe the response payload, determinism, or any limits beyond the schema.

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 front-loaded with the core behavior, and the second sentence immediately bounds the tool. Short fragments for price, endpoint, and payment failure carry useful information for an agent but add the only mild clutter.

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 two-parameter, no-output-schema tool, the description covers purpose, scope boundaries, matching semantics, and payment behavior, which is most of what an agent needs. The main gap is the absence of any description of the response shape (the coverage value and marked fields) given there is no output schema.

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 0%, so the description has to compensate. It clarifies the matching rule (a field is marked when its line or its type line contains one of the supplied directive names), which adds real meaning about how protected_directives are applied, and it maps subgraphs to SDL. It does not explain the subgraph name field or the max/min limits (10 subgraphs, 50,000 char SDL), leaving some parameters under-specified.

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 uses a concrete verb and resource: it counts object and interface fields in the supplied subgraph SDL and marks fields matching the given directive names, with coverage defined as the share of marked fields. It also says what the tool is not ('a text count', does not compose a supergraph, does not decide whether a request would be allowed), which helps separate it from the federation audit siblings. It does not name a specific alternative, so it stops short of 5.

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?

It gives clear negative boundaries: this is a text count, it does not compose a supergraph, and it does not decide whether a request would be allowed, so an agent can tell when this tool is the wrong choice. The payment/execution rules (unpaid calls return 402 and do not run) are also stated. There is no explicit routing to a named sibling for the cases it excludes.

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