layer_infoGet an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Feature/Map Service layer url, e.g. ".../FeatureServer/0". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds valuable context about the return payload (schema fields, geometry type, record count, capabilities) without contradicting annotations. It lacks details on network dependencies or failure modes, but annotations lower the burden.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It efficiently communicates the tool's purpose and output format, earning a top score for conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one simple parameter, no output schema, and strong annotations, the description is largely complete. It details the return items, which is essential since no output schema exists. Minor gaps include not explaining what 'capabilities' encompasses or error behavior, but for a simple getter tool this is acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% (url parameter has a clear description). The description repeats 'by url' but adds no new semantic meaning beyond what the schema already provides. Baseline of 3 is appropriate when schema fully covers the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb ('Get') and resource ('ArcGIS Feature/Map Service layer's schema'), and lists the exact returned items (fields, geometry type, record count, capabilities). This distinguishes it from sibling tools like query_layer, which is likely for data retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when schema information is needed, but does not explicitly state when to use this tool over alternatives or provide exclusions. For example, it does not mention that query_layer should be used for actual data queries, so guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical, while ask_pipeworx_grounded, deep_research, validate_claim, and entity_profile all perform data lookups with only subtle differences. discover_tools and suggest_questions also serve similar onboarding/exploration roles.
Tool names are uniformly snake_case and generally follow a verb_noun or noun_phrase pattern (e.g., ask_pipeworx, query_layer, entity_profile, remember). There is a slight mix between verb-first and noun-first names but no chaotic conventions like camelCase or inconsistent verb tense.
At 34 tools, the count is well above the typical 15-25 range for a coherent server. More critically, the server is named 'Arcgis Lakecountyil' but only 3 tools (search_datasets, layer_info, query_layer) actually relate to ArcGIS; the remaining 31 tools are a broad Pipeworx data platform, creating a severe scope mismatch that makes the count feel excessive and unfocused.
For the ArcGIS domain implied by the server name, the surface is barely complete: it offers search, schema inspection, and querying, but no create, update, delete, or management capabilities. Conversely, the Pipeworx side is relatively rich, but that doesn't match the server's stated purpose, leaving the overall set incomplete for its apparent intended use.