get_collectionGet full metadata for one NASA Earth-science collection by its CMR concept ID — summary, DOI/landing page, spatial coverage, temporal range, and access links. Keyless.
| Name | Required | Description | Default |
|---|---|---|---|
| concept_id | Yes | CMR collection concept ID, e.g. "C1748058432-LPCLOUD" (MODIS/Terra Land Surface Temperature MOD11A1). Get IDs from search_collections. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe, idempotent read operation. The description adds value by specifying the exact metadata fields returned, surpassing the annotation-only baseline.
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 two concise sentences. The first sentence front-loads the purpose and output, the second adds a key usage note. Every word is necessary and there is no redundancy.
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?
Given the tool's simplicity (single parameter, no output schema, and comprehensive annotations), the description is complete. It covers what it returns, how to identify the collection, and the keyless nature. No additional information is needed for effective use.
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 coverage is 100% for the single parameter 'concept_id', with a clear description and example. The description adds context by mentioning that the ID can be obtained via search_collections, providing guidance beyond the schema definition.
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 full metadata for a single NASA Earth-science collection using a CMR concept ID. It lists specific fields (summary, DOI, spatial coverage, etc.) and notes it's keyless, which distinguishes it from sibling tools like search_collections that return multiple collections.
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 you have a known concept ID and want detailed metadata, but it does not explicitly state when to use this tool versus alternatives like search_collections. The 'keyless' hint is helpful but not a full guideline on context or exclusions.
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.
The tool set mixes NASA-specific tools with a large number of financial and prediction market tools, causing confusion. Within the non-NASA tools, there is significant overlap (e.g., multiple Polymarket analysis tools, several research tools with vague boundaries).
Most tools use snake_case, but naming patterns are inconsistent: some start with verbs (search_collections, get_collection), others are noun phrases (entity_profile, deep_research). There is no uniform verb_noun convention across the set.
With 33 tools, the count is high. Although it may be appropriate for the underlying domain (data/prediction markets), it is excessive for the server's stated NASA focus, where only 3 tools are relevant.
For a server named 'Nasa Cmr', the tool set is severely incomplete: only three tools cover NASA Earth science (search/granules/collections), lacking any support for missions, datasets, or advanced queries. The non-NASA tools are comprehensive but disconnected from the server name.