Skip to main content
Glama

Fileion

Search articles

search_articles
Read-onlyIdempotent

Search the articles published on Fileion (blog posts and Fileion News) by title. Returns up to 10 articles per page, newest first, with the topic, author name, date and Fileion page address. The article 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_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
typeNoOnly blog posts or only news.
queryYesPart of the article title, e.g. "download manager".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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), and the description adds genuinely new behavior: 10 results per page, newest-first ordering, the exact fields returned, and the important limitation that article text is not returned. It does not discuss empty-result behavior or matching rules beyond title, so it stops short of a 5.

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?

Three short sentences with the resource and matching field front-loaded, then output shape, then the key limitation. No redundancy or filler; each sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description fully compensates by describing result count, ordering, and returned fields, plus warning that article body text is unavailable. An agent has everything needed to call it and interpret the response.

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 all three parameters are already documented, including the type enum and page minimum. The description only reinforces title-based matching and per-page sizing without adding syntax or format details the schema lacks, so the baseline 3 applies.

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 (search) and resource (articles published on Fileion, blog posts and Fileion News), plus the matching field (title). This clearly separates it from siblings like search_questions, search_software, and search_tools, which target different resources.

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: searching matches only titles, and full text must be read on the page, which acts as a useful boundary condition. However, it never says when to prefer this over other search tools or when not to use it, leaving the agent to infer routing from the resource name alone.

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