Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ce que contient la base viraldar

infos_base

Retrieve available themes, languages, recommended rules, and last export date before filtering viral posts by theme; optionally list frequent words for a chosen theme. No quota cost.

Instructions

Les thèmes (clés d'étiquettes à passer aux autres outils, avec leur nom et leur nombre de posts), les langues, les règles chiffrées (recommandés, critères) et la date du dernier export. Ne coûte rien sur le quota. À appeler avant de filtrer par thème. Avec theme, donne aussi les mots les plus fréquents de ce thème (idées de mots à chercher).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "infos_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNoClé d'un thème ('' = toute la base) pour ses mots fréquents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does more than most: it discloses that the call costs nothing against the quota, that the response is a reference catalog, and that supplying `theme` triggers extra output. It does not mention whether authentication (via the `connexion` sibling) is required first, which is a residual gap.

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?

The payload (what it returns) is front-loaded in the first sentence, followed by short scoping and quota notes and one conditional note. Parentheticals are dense but each carries information; nothing is filler.

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 single-optional-parameter reference tool with no output schema, the description covers returned content, quota cost, call ordering, and conditional behavior — enough for an agent to invoke it confidently. Only authentication requirements and result shape details are absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it says the theme keys come from this tool's own theme list and that passing one yields the most frequent words as search ideas, clarifying the dependency chain. The '' = whole base behavior is left to the schema.

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?

The description enumerates exactly what the tool returns: theme keys with names and post counts, languages, numeric rules, and last export date. That is a specific resource inventory, not a restatement of the name. It does not explicitly contrast itself with the sibling `mes_themes`, so sibling differentiation is only implied by 'clés d'étiquettes à passer aux autres outils'.

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?

'À appeler avant de filtrer par thème' gives an explicit sequencing cue, and the conditional sentence explains when to supply `theme`. What is missing is a when-not condition, such as how this differs from `mes_themes` or `methode`, which an agent might reasonably confuse it with.

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

Deploy Server

Other Tools