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?
The description adds behavioral context beyond the annotations by specifying the exact contents of the returned schema (fields, geometry type, record count, capabilities). Since annotations already declare it read-only and idempotent, this extra detail helps the agent understand the result shape.
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?
One sentence, front-loaded with the verb 'Get', and no filler. Every word contributes to defining the tool's output.
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?
For a single-parameter read-only tool, the description is comprehensive: it names the input and all outputs. The lack of an output schema is mitigated by listing the return contents explicitly.
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?
The input schema fully documents the single 'url' parameter with a clear description and example. The tool description does not add parameter semantics beyond restating 'by url', so baseline of 3 applies.
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 retrieves an ArcGIS layer's schema, listing specific outputs (fields, geometry type, record count, capabilities). This strongly distinguishes it from sibling tools like query_layer, which presumably queries data rather than metadata.
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 this tool is for schema inspection but does not explicitly state when to use it versus alternatives like query_layer. No exclusions or alternative tool references are provided, leaving usage guidance to inference.
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, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical, and several Polymarket analysis tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, bet_research) blur together. The three ArcGIS tools are distinct, but they are drowned out by a large set of data-query and prediction-market tools with unclear boundaries.
All tool names use snake_case, but the verb/noun pattern is mixed: some are command-style (query_layer, validate_claim), some are noun phrases (layer_info, entity_profile), and others are bare verbs (remember, forget). The naming is readable but not consistently patterned.
34 tools is too many for a server named 'Arcgis Allegheny', especially since only three tools (search_datasets, layer_info, query_layer) relate to ArcGIS at all. The bulk of the tools address unrelated domains like Pipeworx data lookups and Polymarket betting, making the count excessive for the apparent purpose.
For a server focused on ArcGIS Allegheny County data, the surface is severely incomplete: only three read-only tools (search_datasets, layer_info, query_layer) cover the domain, and they lack operations like adding, updating, or deleting features. The remaining 31 tools are unrelated to GIS, so the server fails to provide a coherent or complete toolset for its stated purpose.