Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Récupérer un dictionnaire BoondManager

boond_application_dictionary
Read-onlyIdempotent

Retrieve reference dictionaries from BoondManager, including states, types, countries, currencies, languages, tools, and expertise areas by specifying a dot-separated path.

Instructions

Récupère un dictionnaire de référence BoondManager (états, types, pays, devises, langues, outils, expertises, ...).

L'API expose un seul endpoint /application/dictionary qui renvoie tout — le serveur le cache (TTL 1h, configurable via BOOND_DICTIONARY_TTL_MS) et extrait un sous-arbre par chemin dotté.

Args:

  • dictionaryType (string): Chemin dans la réponse (relatif à data). Exemples :

    • "setting.state.{resource,candidate,contact,company,opportunity,project,invoice,order,positioning}" → états par entité

    • "setting.typeOf.{resource,contact,project}" → types par entité

    • "setting.action.{candidate,resource,opportunity,project,...}" → actions disponibles

    • "setting.tool" → outils / technos (Java, AWS...)

    • "setting.expertiseArea" → domaines d'expertise

    • "setting.experience" → niveaux d'expérience

    • "setting.languageSpoken" → langues parlées

    • "setting.activityArea" → secteurs d'activité

    • "setting.mobilityArea" → mobilités géographiques

    • "setting.currency" → devises

    • "setting.civility" → civilités

    • "country" → pays

    • "languages" → langues d'interface (fr, en, es)

Note : l'ancienne forme "states/resources" (slash) n'est pas valide — utilisez "setting.state.resource".

Retourne le sous-arbre (souvent un tableau {id, value, ...}) ou isError: true si le chemin est introuvable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dictionaryTypeYesType de dictionnaire (ex: typeOf/actions, typeOf/absences, states/candidates, states/resources, states/opportunities, states/projects, states/invoices, countries, currencies, languages...)

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable details: the endpoint caches responses with configurable TTL (1h), extracts a subtree, and returns isError on invalid path. No contradiction.

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 description is relatively long but well-organized: purpose, caching info, parameter examples in bulleted list, and a note about deprecated syntax. Each section adds necessary information, though it could be slightly more concise.

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?

With no output schema, the description adequately explains the return format (subtree array with id, value, etc.) and error behavior. Caching details and parameter examples cover all necessary information for tool usage.

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 description coverage is 100%, but the tool description adds significantly more value: concrete examples of all valid paths, notes on syntax (old vs. new format), and expected return structure. This greatly aids correct parameter selection.

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 retrieves a reference dictionary from BoondManager. It lists many example paths like setting.state.resource, country, etc., which distinguishes it from sibling tools that handle specific entities.

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 provides extensive examples of when to use specific dictionaryType values and notes the correct dotted-path format, implicitly guiding usage. It does not explicitly state when not to use it, but the context of sibling CRUD tools makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fauguste/boondmanager-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server