Skip to main content
Glama
O meu voto

O meu voto

Locais de votação da cidade

search_polling_places
Read-onlyIdempotent

Find polling places in a Brazilian municipality by neighborhood, name, or address, and rank them by distance when coordinates are provided; useful if you don't know your zone or section.

Instructions

Lista os locais de votação de um município, com filtro por bairro, nome do local ou endereço, e ordenados pela distância a um ponto quando o cliente informa coordenadas. Para quem não sabe a zona e a seção.

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": {
      "uf": "<uf>",
      "municipality": "<municipality>"
    },
    "name": "search_polling_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufYesSigla da UF, 2 letras: estados, DF ou ZZ para o exterior
nearNoCoordenadas do eleitor; ordena por distância. Sem geocodificação
limitNo1 a 50; padrão 20
queryNoTexto que casa com o nome do local ou o endereço
roundNoTurno, opcional; sem ele, o próximo turno já publicado pelo TSE
offsetNoInício da página
municipalityYesNome do município (com ou sem acento) ou código TSE
neighborhoodNoBairro, opcional

Output Schema

NameRequiredDescriptionDefault
dataYes
sourceYes
electionYes
warningsYesAvisos ao eleitor, em PT-BR; pode ser vazia
not_foundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context by stating results are ordered by distance when coordinates are supplied, but that ordering is also disclosed in the "near" schema description, and pagination/limit behavior is left entirely to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. Scope, filters and ordering come first, and the audience/routing hint is placed last where it is most useful.

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?

An output schema exists, so return values need not be described, and the description covers scope, filters, ordering and audience. Minor gaps remain around pagination (offset/limit) and how multiple filters combine, which the schema documents but the description does not synthesize.

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%, so every one of the 8 parameters is already documented (including the round default and limit range). The description restates the filter dimensions (bairro, nome, endereço, coordenadas) but adds no syntax, format or interaction detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource ("Lista os locais de votação de um município") and immediately scopes it with the available filters (bairro, nome, endereço) and the distance-ordering behavior. The closing line ("Para quem não sabe a zona e a seção") implicitly separates it from find_polling_place, which serves users who do know their zone/section.

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?

"Para quem não sabe a zona e a seção" gives a clear condition for choosing this tool over a zone/section-based lookup, so the when-to-use case is explicit. It stops short of naming the alternative tool or stating any when-not-to-use condition, so it falls short of a 5.

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