Skip to main content
Glama
0103juan

secop-mcp

by 0103juan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SOCRATA_APP_TOKENNoAn optional Socrata app token that raises the anonymous rate limit for requests to datos.gov.co.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
describe_datasetA

Explain the SECOP II contracts dataset: every queryable column and the known data pitfalls. Call this first.

find_entityA

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.
query_contractsA

Query SECOP II contracts. Returns at most 100 rows.

With aggregates and columns together, rows are grouped by the columns (for example
columns=[proveedor_adjudicado, documento_proveedor] with sum of valor_del_contrato gives the
total per supplier). Filters are combined with AND; 'contains' is a case-insensitive
substring match on a text column. Dates are AAAA-MM-DD. order_by takes a requested column
or an aggregate alias such as sum_valor_del_contrato or count.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

The three tools serve clearly separate roles: describe_dataset is schema discovery, find_entity resolves an entity name to a NIT against a local directory, and query_contracts runs the actual data query. The find_entity description explicitly clarifies it does not touch the dataset, removing any overlap with query_contracts.

Naming Consistency5/5

All three names follow a clean verb_noun snake_case pattern (describe_dataset, find_entity, query_contracts) with no stylistic deviations or mixing of conventions.

Tool Count4/5

Three focused tools for a single-domain dataset server is well-scoped—each one (understand schema, resolve entity, query) earns its place with no redundancy. It leans slightly minimal, but the workflow is coherent.

Completeness4/5

The surface covers the core lifecycle for a data query server: understand the schema, resolve entities, and query with filters/aggregates/ordering. A few gaps remain, such as no distinct-values helper or paging beyond the 100-row cap, but agents can work around them.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources