Skip to main content
Glama
Sign In
ostrov-mcp

ostrov-mcp

by iia-arg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_objects

Read-onlyIdempotent

Retrieve public object details and availability rules from ostrov-mcp to check resource information; open places are not guaranteed.

Instructions

Current public resource descriptions and availability rules; no guarantee of open places.

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": "get_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral caveat – that availability data carries 'no guarantee of open places' – which is freshness/accuracy context the annotations do not convey. It stops short of anything else, such as scope or staleness timing.

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?

A single short sentence with no padding, so nothing wastes the agent's attention. It reads as a noun-phrase fragment rather than a stated action, which slightly weakens the front-loading but keeps it tight.

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?

With no output schema, no parameters, and no annotations explaining return shape, the description should do more to explain what a caller receives and how it relates to siblings like get_catalog. The availability caveat is helpful, but an agent still cannot confidently predict the response.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is no parameter behavior the description could usefully add. Schema coverage is 100% with an empty property set, so nothing is missing.

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

Purpose3/5

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

The description gestures at the content ('public resource descriptions and availability rules') but never defines what an 'object' actually is in this domain, so the verb+resource pairing stays vague. It also gives no differentiation from siblings like get_catalog or get_center, which could plausibly return overlapping data.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. With six sibling tools available, the agent is left to guess whether this is the right entry point.

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