Skip to main content
Glama

4fillment

Ask 4fillment

ask_4fillment
Read-onlyIdempotent

Answers a question about 4fillment from its approved answers, each with its source. When there is no approved answer it says so: do not guess, offer a person at 4fillment instead.

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": {
      "question": "<question>"
    },
    "name": "ask_4fillment"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe question as the user asked it.

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 cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds behavior beyond them: answers are drawn from an approved corpus and carry sources, and the tool will openly report the absence of an approved answer rather than fabricate one. What it does not disclose is the shape of the response (how sources are presented, whether multiple candidate answers come back), which matters since 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.

Conciseness5/5

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

Two short sentences with zero waste, front-loading what the tool returns before the fallback rule. Nothing needs to be moved or cut.

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 one-parameter, read-only, closed-world lookup tool the definition covers purpose, source attribution, and the no-answer branch, which is the main thing an agent could get wrong. The only real gap is return-format detail, made more noticeable by the absence of an 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?

The single parameter is fully documented in the schema (coverage 100%), including length bounds. The description only adds the domain framing that the question is about 4fillment and that it should be passed as the user phrased it. Useful but minimal; baseline 3 is appropriate when the schema carries the parameter semantics.

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 and resource: answers a question about 4fillment from approved answers, with sources attached. It also implicitly sets itself apart from the escalation sibling by saying it will point to a person when no approved answer exists, so an agent can tell what kind of tool this is without opening the schema.

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?

Gives an explicit when-not path: if there is no approved answer, do not guess and offer a person at 4fillment instead. That is real routing guidance for the failure case. It falls short of 5 because it does not name the escalation sibling (ask_a_person) explicitly, leaving the agent to map 'a person at 4fillment' onto a tool.

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