Skip to main content
Glama
Sign In
geo-osiris-mcp

geo-osiris-mcp

by osviel91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_imports

List staged geospatial imports, optionally filtering by layer to locate specific datasets.

Instructions

List staged imports, optionally filtered by layer.

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_imports"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
layer_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry behavioral disclosure, but it only states a listing action and the 'staged' status. It does not mention pagination, ordering, whether only pending/in-flight imports are returned, or any read-only guarantee.

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?

One tight sentence front-loads the verb and resource and packs the key filter into a dependent clause. There is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple optional-parameter list operation with an output schema, this is minimally viable. However, without any parameter descriptions or usage notes, an agent gets only the core list/filter behavior from the text.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It adds meaning only for layer_id ('filtered by layer'); limit and cursor are left to be inferred from their names and defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and object ('List staged imports') and adds the key optional filter by layer. It is clear enough to stand apart from siblings like list_sources and list_import_rows, but it does not explicitly name or contrast those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to choose this tool over get_import, list_import_rows, or summarize_import. The only implication is that import lists can be filtered by layer, so an agent must infer the rest from sibling names.

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