CSolar Energia

Conferir área atendida

check_service_area

Read-only

Diz se um município está na área atendida pela CSolar Energia para instalação de energia solar. A área atendida é o estado de São Paulo (645 municípios). Informe o município e, se souber, a UF. Não pede nem guarda dados pessoais.

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": {
      "cidade": "<cidade>"
    },
    "name": "check_service_area"
  }
}

Input Schema

Name	Required	Description	Default
`uf`	No	UF do município, opcional (ex.: SP). Ajuda quando há municípios com o mesmo nome em outros estados.
`cidade`	Yes	Nome do município, por exemplo Sorocaba.

Output Schema

Name	Required	Description
`uf`	Yes
`mensagem`	Yes
`situacao`	Yes
`municipio`	Yes	Nome oficial do município, quando está na lista do site.
`saiba_mais`	Yes	Página do município no site, quando está na área atendida.
`area_atendida`	Yes
`fale_com_a_csolar`	Yes	Contato com a equipe; null quando é de fora da área.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world). The description adds genuinely useful behavioral context beyond that: the coverage boundary is strictly São Paulo, and the tool 'não pede nem guarda dados pessoais', which reassures on privacy handling for a lookup that takes a place name.

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?

Three short sentences, front-loaded with what the tool determines and the scope boundary, then input guidance, then the privacy note. Every sentence carries information an agent can act on; no filler.

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 simple boolean coverage check with an output schema and full annotation coverage, the description supplies purpose, business-rule scope, input guidance, and privacy behavior. The only omission is the relationship to the sibling tool, which is a minor gap given the low complexity.

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 the schema already documents both parameters, including why uf is optional and helpful for disambiguation. The description's 'se souber, a UF' merely restates that optionality, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Diz se um município está na área atendida pela CSolar Energia') and even defines the scope of that area (state of São Paulo, 645 municipalities). It does not explicitly name or contrast with the sibling estimate_solar_system, but the function is unambiguously different from an estimation tool.

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?

The description implies when to use it (to check coverage for solar installation) and instructs on inputs ('Informe o município e, se souber, a UF'), but it never states when NOT to use it or routes the agent to estimate_solar_system as the follow-up. Usage is implied rather than spelled out.

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

All CSolar Energia tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?