Skip to main content
Glama
0103juan

secop-mcp

by 0103juan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

find_entity

Look up a Colombian state entity by name to retrieve its NIT from a local directory. The search ignores case and accents, and requires all words to appear in the entity's registered name.

Instructions

Find a state entity by name and get its NIT. Immediate: it searches a local directory, not the dataset.

Case and accents are ignored, and every word must appear in one of the entity's names. Entities
are registered under their legal name: a city government ("Alcaldía de X") is often MUNICIPIO DE X
or DISTRITO ... DE X, and a "Gobernación" is often DEPARTAMENTO DE X. So when nothing has every
word, the search is repeated without the kind of entity and match says "place_only": check the
names before choosing. The directory is a snapshot; an entity that started publishing recently
may be missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 behavioral burden and does well: it discloses case/accent insensitivity, the all-words matching rule, legal-name conventions, fallback behavior with 'place_only' matches, and snapshot limitations. It omits the effect of the 'limit' parameter, which is a minor 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 description is front-loaded with the core action, then adds dense but relevant detail about matching rules and naming conventions. It is somewhat long but every sentence contributes useful context.

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-parameter lookup tool with no annotations and no output schema, the description is nearly complete: it covers search behavior, edge cases, and limitations. The only notable omission is the semantics of the 'limit' parameter.

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 coverage is 0%, so the description must compensate. It adds meaningful matching semantics for the 'name' parameter (case/accent ignoring, all-words requirement, legal-name conventions) but says nothing about the 'limit' parameter's purpose or default.

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 opening sentence states a specific verb and resource: 'Find a state entity by name and get its NIT.' It also distinguishes its scope from the dataset ('it searches a local directory, not the dataset'), which differentiates it from sibling tools like query_contracts.

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 explains when the fallback search triggers ('when nothing has every word') and advises checking names before choosing. It clarifies the search is against a local directory rather than the dataset, but does not explicitly name alternative tools or state when to prefer them.

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