Skip to main content
Glama

BlockSentient directory tools

Get methodology

get_methodology
Read-onlyIdempotent

Returns what the CTI score measures and what it does not, the section weights and grades, what each value such as 'Not documented' means, how prices should be read and what the visit link is.

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": "get_methodology"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety needs no restating. The description adds what the annotation cannot: that the payload is static explanatory content covering score scope, weights, grades, value semantics, price conventions and the visit link — effectively describing return contents in the absence of an 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that leads with the core outcome ("what the CTI score measures and what it does not") before the supporting content list. No filler, no restatement of the tool name, and every clause names a distinct piece of returned content.

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?

With no parameters and no output schema, the description carries the burden of explaining return content, and it does so by enumerating the sections covered. The only gap is that it does not indicate the shape or key structure of the returned document, though the topical coverage is sufficient to call the tool confidently.

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. It also correctly introduces no phantom arguments, consistent with the empty object schema.

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 ("Returns") and resource (the methodology behind the CTI score), then enumerates the exact content: score scope, section weights and grades, value definitions such as 'Not documented', price interpretation, and the visit link. That enumeration makes it unmistakably a reference/glossary tool, clearly separable from product-facing siblings like get_product or compare_products.

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?

Usage is implied rather than stated: by listing what each score value and price convention means, the description signals it should be consulted to interpret output from the product tools, but it never says so explicitly. There is no statement of when to call it, no ordering relative to get_product/compare_products, and no exclusions.

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