Skip to main content
Glama

Piqline (open door)

Professions Piqline has a page for

piqline_professions
Read-only

Lists the professions that have a dedicated Piqline page (French, English or German), optionally filtered by a few words. No cost, no model.

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": "piqline_professions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoA few words, e.g. 'real estate' or 'creator'.
languageNoLanguage of the list. Default: fr.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context with 'No cost, no model' (no LLM inference involved) and the language coverage, but says nothing about result volume, pagination, or whether a miss returns empty. Useful additions on top of annotations, not rich behavioral disclosure.

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?

A single tight sentence that leads with the core action and scope before the qualifier. The trailing fragment 'No cost, no model' is terse to the point of being cryptic, but nothing is wasted.

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 two-optional-parameter read-only listing tool with no output schema, the description covers what it returns (a list of professions) and the filter dimensions. The main residual gap is that it never indicates what a list entry contains or how the keyword matches, which an agent may want before composing a call.

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%: 'query' already carries the 'a few words, e.g. real estate or creator' example and 'language' carries the enum plus default. The description only restates 'optionally filtered by a few words' and the three languages, adding no syntax, matching behavior, or empty-result semantics beyond 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?

Names a specific verb and resource ('Lists the professions that have a dedicated Piqline page') and bounds the scope by page language. It implicitly separates itself from the AI-style siblings via 'No cost, no model', but never names an alternative tool directly.

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 only implied: an agent can infer this is the browse/discover tool for checking whether a profession has a page, and the optional 'query' hint suggests keyword lookup. There is no explicit statement of when to prefer piqline_for or piqline_ask instead, and no exclusions.

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