Skip to main content
Glama

Semerenko Group Public Site MCP

One listing by id

sem.get_property
Read-only

Full record of one published listing on semerenkogroup.com by its numeric id, with listing_url and inquiry_url.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "sem.get_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesListing id from sem.search_properties.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful constraint that only published listings are returned, but says nothing about behavior for unknown ids (error vs empty) or what fields the record contains beyond the two URLs.

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 front-loaded sentence naming the resource, the lookup key, and two returned fields with no filler. Nothing is redundant, though the trailing URL clause is only loosely integrated.

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 one-parameter read with no output schema, the description covers what the tool returns at a high level and the published-only constraint. It leaves gaps around not-found handling and the rest of the record's shape, which matter since there is no output schema to consult.

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

Parameters3/5

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

Schema coverage is 100% and the single id parameter is already documented, including its provenance from sem.search_properties. The description only reaffirms that the id is numeric and must reference a published listing, adding marginal meaning over the schema.

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?

States a specific action and resource: retrieves the full record of one published listing by numeric id on a named site. It is clearly a single-item lookup, implicitly contrasted with the search sibling, but it never names or distinguishes that sibling in the description text.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase 'one published listing... by its numeric id' tells the agent this is a by-id retrieval, and the qualifier 'published' hints that unpublished records are out of scope. It gives no explicit when-to-use, when-not, or pointer to an alternative such as a search tool for discovering ids.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources