Skip to main content
Glama

Fmind Freelance AI Architect Website

by io.github.fmind
OverviewDiscussionsAdmin

Search articles

search_articles
Read-only

Search the hosted articles by relevance (BM25 over titles, tags, descriptions, and full text) and return the best matches. Use it to answer what Fmind has written about a topic instead of listing every publication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNooptionally keep only articles with this tag, case-insensitive: Agent, Coding, LLM, RAG, MLOps, Cloud, Python, Project, Demo, Guide
limitNomaximum number of results to return (default 10, maximum 50)
queryYeswords to search for across article titles, tags, descriptions, and full text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
totalYes
articlesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tag
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "optionally keep only articles with this tag, case-insensitive: Agent, Coding, LLM, RAG, MLOps, Cloud, Python, Project, Demo, Guide",
+  "title": "Tag"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / default
      Previous value: -0New value: +10
  3. 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=true, so the safety profile is covered. The description adds meaningful behavioral detail beyond that: it reveals the ranking mechanism (BM25) and the set of fields searched, which helps an agent understand what matches and how results are ordered. This goes beyond the annotations without contradicting them.

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 sentences, zero filler. The first sentence states the mechanism and behavior; the second gives the intended use case and differentiates from listing. Everything earns its place.

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?

Given the simple 3-parameter schema, the presence of an output schema, and the read-only annotation, the description covers the core purpose, usage guidance, and matching behavior. It lacks only minor details like handling of empty queries or sorting edge cases, but those are not necessary for correct tool selection and invocation.

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 description coverage is 100%, and the schema already explains query, tag, and limit in detail, including defaults, max, and tag enum values. The description does not add new parameter-level meaning beyond restating the searchable fields, so the baseline of 3 is appropriate.

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?

The description states a specific action ('Search'), a specific resource ('hosted articles'), and a clear scope (BM25 over titles, tags, descriptions, and full text). It also distinguishes itself from listing every publication, which maps to a sibling tool, making its purpose unmistakable.

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?

The description gives an explicit use case ('answer what Fmind has written about a topic') and an implicit alternative ('instead of listing every publication'). It does not name the sibling tool (list_publications) directly, but the guidance is clear and actionable without being vague.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fmind Freelance AI Architect Website toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources