Skip to main content
Glama

faf_score

Score a .faf 0-100 with the always-33 faf-kernel, the same score faf-cli gives (Rust→WASM, at the edge).

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

Input Schema

NameRequiredDescriptionDefault
contentYesRaw .faf file content (YAML)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds useful behavioral context by stating the score is deterministic ('always-33 faf-kernel') and matches faf-cli output, but it does not disclose error behavior, whether the operation is read-only, or any execution details beyond the 'Rust→WASM, at the edge' tagline.

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 a single front-loaded sentence that immediately conveys the tool's action and output scale. However, the phrase 'Rust→WASM, at the edge' is marketing-oriented jargon that does not meaningfully help an agent invoke the tool correctly.

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 simple one-parameter scoring tool with no output schema, the description explains the return scale (0-100) and the scoring engine, which is enough to understand the result. Greater completeness would require error or edge-case behavior, but the core call semantics are clear.

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 the schema already documents the sole 'content' parameter as raw .faf YAML. The description adds no parameter semantics beyond what the schema provides, making the baseline 3 appropriate.

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 gives a specific verb and resource: scoring a .faf file on a 0-100 scale using a named faf-kernel. It does not explicitly distinguish itself from the sibling tools faf_read and faf_validate, though the scoring purpose is still clear.

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?

The description offers no guidance on when to use this tool versus faf_read or faf_validate, nor any prerequisites, exclusions, or workflow context. The mention of faf-cli parity is not usage guidance.

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.