Skip to main content
Glama
Sign In

Free2AITools

by com.free2aitools
OverviewDiscussionsAdmin

free2aitools_explain

Explain why one specific entity received its FNI score, returning the 5-factor breakdown: Semantic (S), Authority (A), Popularity (P), Recency (R), Quality (Q). FNI = 0.35S + 0.25A + 0.15P + 0.15R + 0.10*Q (the S factor is a baseline, surfaced with a caveat, not a measured per-entity value). USE WHEN you already have one entity id (from a search/rank/select result) and want its score rationale. DO NOT USE to search/discover entities, to run a model, or to get a recommendation — this only describes scoring evidence for the caller to interpret. Read-only, no side effects, no billing. Use free2aitools_compare instead for side-by-side differences across multiple entities.

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": {
      "id": "<id>"
    },
    "name": "free2aitools_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntity name or ID to explain (e.g. "Llama-3", "hf-model--meta-llama--llama-3-8b")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Entity name or ID to explain (e.g. \"Llama-3\")"New value: +"Entity name or ID to explain (e.g. \"Llama-3\", \"hf-model--meta-llama--llama-3-8b\")"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description fully covers behavioral traits: it states 'Read-only, no side effects, no billing' and clarifies the caveat about the S factor (not a measured per-entity value).

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?

Every sentence serves a clear purpose, explaining function, usage, limitations, and formula. It is slightly verbose but well-structured and front-loaded with the core action. No wasted words.

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?

Given the complexity of the scoring formula and the absence of an output schema, the description completely covers all aspects: purpose, usage, behavioral traits, parameter details, formula breakdown, and caveats. It leaves no ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single required parameter 'id'. The description adds meaning by providing example values like 'Llama-3' and specifying the format 'hf-model--meta-llama--llama-3-8b'.

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 clearly states the tool explains why an entity received its FNI score with a 5-factor breakdown, and includes the formula. It distinguishes itself from sibling tools like free2aitools_compare by specifying its unique purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage guidance: 'USE WHEN you already have one entity id...' and 'DO NOT USE to search/discover entities...'. It also names an alternative sibling (free2aitools_compare) for side-by-side comparisons.

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

All Free2AITools 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