Skip to main content
Glama

STATIC

STATIC overview

static_overview
Read-onlyIdempotent

What SURESOFT STATIC is: the definition and overview from the official STATIC product page, with the list of page sections that static_get_section can return.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "static_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is covered. The description adds that the content comes from the official product page and that it includes a section list consumed by a sibling, which is useful context. It does not describe the shape of what comes back (prose? structured sections?), which matters given there is no output 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?

A single front-loaded sentence that defines the tool's content scope without padding. The phrasing 'What SURESOFT STATIC is:' is slightly unusual as an opener but efficiently signals the subject. Nothing is wasted, though the trailing clause about static_get_section is doing usage-guidance work inside a purpose sentence.

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?

With no parameters, no output schema, and annotations covering safety, the description's remaining duty is to convey the return shape. It says a 'definition and overview' plus a 'list of page sections', but not whether sections are plain names or annotated entries. Adequate orientation, incomplete detail for a read-only lookup tool.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is 100% by construction.

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 concrete resource: the definition and overview taken from the official STATIC product page, plus the list of sections available to static_get_section. That distinguishes it from the sibling section tool by making this the entry-point overview. It stops short of an explicit verb such as 'returns' or 'fetches', leaving the action implied rather than stated.

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?

Naming static_get_section as the consumer of the section list implies this tool should be called first to orient, but the description never says when to use this versus that tool or versus static_list_sections. Usage is inferable rather than stated, which is the minimum-viable level.

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