VISEON for Web

get_entity

Get complete schema.org entity data by URL (its @id), including relationships the graph holds in either direction. Use this before selecting an entity's image or other media: retain the canonical subject ID and use only assets explicitly linked by the retrieved record. A matching name, caption or filename alone does not establish identity. If no supported asset is available, state the limitation; do not add externally searched media to a KG-grounded answer.

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": {
      "url": "<url>"
    },
    "name": "get_entity"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026
- removedInput schema / properties / url / description
```
Removed value: -"Full URL of the entity"
```
First observedSep 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses retrieval scope: complete entity data plus relationships in either direction. It also adds important constraints around identity and media use. It does not describe auth, rate limits, or not-found behavior, but the output schema covers return structure.

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 purpose is front-loaded and the description is four sentences with no obvious repetition. Each sentence serves purpose, usage, identity warning, or fallback guidance, though it is somewhat dense for a one-parameter retrieval tool.

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?

Given one required parameter and an output schema, the description covers what data is retrieved, how it should be used for media selection, and the identity caveat. The main gaps are routing guidance when the URL/@id is unknown and behavior when the entity is not found.

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 description coverage is 0%, so the description must explain the single required parameter. It does meaningfully identify 'url' as the entity's @id URL and warns that a matching name alone is not sufficient, but it gives no URL format example or further validation detail, so compensation is partial.

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 states a specific verb and resource: get complete schema.org entity data by URL (its @id), including relationships in either direction. It implicitly separates exact-ID retrieval from fuzzy/find/search siblings by emphasizing URL/@id, but it never names an alternative, so full sibling differentiation is absent.

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?

It gives clear usage context: use this before selecting an entity's image or other media, retain the canonical subject ID, and do not treat matching name/caption/filename as identity. It also says to state the limitation if no supported asset exists and not to add externally searched media. However, it does not explain when to use this versus fuzzy_find_and_traverse or search_content if the URL/@id is unknown.

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

All VISEON for Web tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.