Skip to main content
Glama
Sign In

index

by com.isoligne
OverviewDiscussionsAdmin

A sector ranking

secteur
Read-onlyIdempotent

Returns the published sites of a sector, grouped by level and ordered by score alone. Scores less than 5 points apart are not separated. The ranking covers published sites only, not the whole market. Isoligne decides which sites are published, after notifying each company; client status plays no part in inclusion or order.

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

Input Schema

NameRequiredDescriptionDefault
secteurYessector key from secteurs_disponibles, e.g. assurance

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / secteur / description
      Previous value: -"ex. assurance, logiciel"New value: +"sector key from secteurs_disponibles, e.g. assurance"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read. The description goes well beyond them, disclosing that Isoligne decides publication after notifying each company, that client status affects neither inclusion nor order, and that scores within 5 points are not separated. It omits only the shape of what is returned.

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?

Four tight sentences with the output behavior front-loaded and no filler. The Isoligne sentence is arguably marginal but it carries real inclusion semantics, so it 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?

With one required parameter and no output schema, the description must carry the return semantics, and it does explain grouping by level and score-based ordering with tie handling. What is missing is the actual structure of a returned entry (site fields, score field), which the agent must still infer.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains it is a sector key from secteurs_disponibles with an example. The description adds nothing about the parameter, so the baseline of 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?

The description states a specific verb and resource: it returns a sector's published sites, grouped by level and ordered by score. It also pins the scope (published sites only, not the whole market). It does not name or distinguish itself from siblings like secteurs_disponibles, so it stops short of a 5.

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: the ranking covers published sites only, which tells the agent this is not a market-wide listing. There is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling tool that supplies the sector key.

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

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