Skip to main content
Glama

Fileion

Search questions

search_questions
Read-onlyIdempotent

Search the questions asked on Fileion Q&A by their title. Returns up to 10 questions per page, newest first, with the number of answers, whether one was accepted, and the Fileion page address. The answers' text is not returned: read it on the page.

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": {
      "query": "<query>"
    },
    "name": "search_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
queryYesPart of the question title, e.g. "install vlc".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: newest-first ordering, a hard cap of 10 per page, the returned fields (answer count, accepted flag, page address) and the important limitation that answer text is not returned. These additions are real but modest given the annotation coverage.

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?

Four short sentences, front-loaded with purpose before return contents and then the answer-text exclusion. Every sentence carries information an agent needs; nothing is padded or repeated from the title.

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 output schema, the description must carry return-value information and mostly does: item fields, ordering, page size and the answer-text exclusion. It stops short of saying how an agent knows whether more pages exist or whether results are ranked by relevance, which matters for a paginated search tool.

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% and both parameters are documented there, including the title-substring example. The description only restates that matching is on titles and that pages yield up to 10 results; it adds no syntax or matching-rule detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: search questions on Fileion Q&A, matched by title. The resource ('questions') is distinct from the sibling search tools (search_articles, search_software, search_tools), so an agent can discriminate by resource name, although no alternative is named explicitly.

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?

The title-only matching constraint is implied clearly ('by their title'), which tells an agent this is not a full-text search, but there is no explicit when-to-use versus when-not guidance and no mention of the sibling search tools or of what to do when no match is found.

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