Skip to main content
Glama
Sign In
LeadAce

LeadAce

by aitit-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_country_codes

List ISO country codes with send-allowed flags to identify regions where outreach can be delivered.

Instructions

Lists the ISO 3166-1 alpha-2 country codes LeadAce recognizes for a prospect/organization country. Returns { countries: [{ code, name, sendAllowed }], sendAllowed, note }; sendAllowed marks codes outreach can currently deliver to, others store but are blocked at send time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_country_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.54

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It covers the return shape and the semantics of sendAllowed, including that non-allowed codes 'store but are blocked at send time.' This is valuable behavioral context beyond the bare tool 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?

Two sentences with no filler. The first sentence states what the tool lists; the second explains the return object and the key behavioral distinction. Every word contributes.

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?

For a zero-parameter, reference-style tool with no output schema, the description is complete: it names the standard, the domain, the exact return fields, and the meaning of sendAllowed. The agent has enough information to invoke and interpret this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameters, so the baseline is 4. The description correctly avoids inventing parameter details and instead provides output semantics. Its mention of the 'country' context is useful but not a parameter definition.

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 uses a specific verb ('Lists') and a precise resource ('ISO 3166-1 alpha-2 country codes LeadAce recognizes'), with additional scope defined as 'for a prospect/organization country.' This is clearly distinct from any sibling tool in the set.

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 clear context for when this tool is relevant: when working with country values for prospects/organizations. It also explains the meaningful distinction between sendAllowed and blocked codes, which helps the agent decide how to use the results. No explicit alternatives or exclusions are given, but no competing sibling tool exists.

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