Skip to main content
Glama

save_to_shortlist

Save a site with its objectives and current score to a persistent shortlist for later re-scoring against the evolving national baseline.

Instructions

Save a site into a PERSISTENT, named shortlist that survives across conversations (Phase 5 statefulness). Snapshots the site's objectives + its current percentile objective_score, so you can re-score it later against the evolving national baseline. Use to build a durable siting shortlist across days/weeks; the list is scoped to your API key. Pair with get_shortlist to re-score + see drift. site should carry lat/lng/capacity_mw + the analyze_site metric fields (risk_resilience, fiber_connectivity, water score, etc.) you ranked on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesSite object: {site_ref?, lat, lng, capacity_mw, <metric fields from analyze_site>} — the metrics are what get re-scored later
notesNoOptional free-text note, e.g. "strong fiber, acceptable water"
objectivesYesThe {field: signedWeight} objectives this site was ranked under (+maximize/-minimize) — stored so re-scoring uses the same criteria
shortlist_nameNoName of the shortlist, e.g. "Q3-2026-1GW-targets" — created if new
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds context about persistence across conversations, snapshotting objectives and scores, and API key scoping, which goes beyond annotations. No contradictions.

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

Conciseness4/5

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

The description is detailed and front-loaded with the main purpose. Every sentence provides useful information, though slightly verbose. Could be tightened by removing redundant phrases like the parenthetical in 'site should carry...'.

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?

The description covers lifecycle (save then pair with get_shortlist), persistence, scoping, and required fields. However, it lacks details on return value (no output schema) and error conditions, which are minor gaps for a single-purpose tool.

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

Parameters5/5

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

Schema descriptions cover all four parameters (100% coverage). The description adds extra meaning, such as the site needing lat/lng/capacity_mw and metrics for re-scoring, and that objectives are stored for consistent re-scoring. This adds significant value beyond the schema.

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 clearly states the tool saves a site into a persistent named shortlist, distinguishing it from temporary saves or retrievals. It specifies the verb 'save' and resource 'site into shortlist', and contrasts with sibling tools like 'save_site' and 'get_shortlist'.

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 explains when to use the tool (building a durable shortlist across days/weeks) and suggests pairing with get_shortlist for re-scoring. It provides context on site requirements but does not explicitly mention when not to use or alternatives like temporary saves.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azmartone67/dchub-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server