GREENLANDAI

entity_state

Read-only

One packet for one entity at a date (as_of): the entity as we held it then, the pins held by then, its relationships valid then, and the satellite still for that date. Charged for the parts delivered. Agent keys only. Metered: see CHARGING in the server instructions; quote first with billing_quote.

Input Schema

Name	Required	Description
`id`	Yes	The entity's numeric id. Required.
`as_of`	No	The date of the packet, YYYY-MM-DD. Default today.
`max_cloud`	No	Maximum cloud cover of a scene, 0-100 percent. For the still. Default 20.
`radius_km`	No	Radius for the nearby pins, in km. Default 25.
`entity_type`	Yes	Entity kind: deposit \| infrastructure \| company \| project. Required.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 29, 2026
- removedInput schema / properties / as_of / default
```
Removed value: -null
```
- removedInput schema / properties / as_of / title
```
Removed value: -"As Of"
```
- removedInput schema / properties / entity_type / title
```
Removed value: -"Entity Type"
```
- removedInput schema / properties / id / title
```
Removed value: -"Id"
```
- removedInput schema / properties / max_cloud / title
```
Removed value: -"Max Cloud"
```
- removedInput schema / properties / radius_km / title
```
Removed value: -"Radius Km"
```
- removedInput schema / title
```
Removed value: -"entity_stateArguments"
```
- removedOutput schema / title
```
Removed value: -"entity_stateDictOutput"
```
Changed2 schema fields changedOct 29, 2026
- addedInput schema / properties / id / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  }
+]
```
- removedInput schema / properties / id / type
```
Removed value: -"string"
```

Changed5 schema fields changedOct 17, 2026

addedInput schema / properties / as_of / description

Added value: +"The date of the packet, YYYY-MM-DD. Default today."

addedInput schema / properties / entity_type / description

Added value: +"Entity kind: deposit | infrastructure | company | project. Required."

addedInput schema / properties / id / description

Added value: +"The entity's numeric id. Required."

addedInput schema / properties / max_cloud / description

Added value: +"Maximum cloud cover of a scene, 0-100 percent. For the still. Default 20."

addedInput schema / properties / radius_km / description

Added value: +"Radius for the nearby pins, in km. Default 25."

AddedOct 4, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: it is charged for parts delivered, requires agent keys, and is metered with a recommendation to quote first via billing_quote. This covers cost and auth needs, which annotations do not provide. It stops short of describing failure modes or rate limits, but the added information is substantial.

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 description is front-loaded with the core purpose and return contents, followed by billing and auth notes. It is efficient, though slightly dense with multiple sentences. Every sentence serves a purpose, but minor tightening could improve flow.

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 the presence of an output schema and annotations covering safety, the description is largely complete for correct invocation. It covers billing and auth needs, and the output schema handles return values. The main gap is the lack of usage guidance versus alternatives, but that is scored separately.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description mentions as_of and implies the components corresponding to radius_km and max_cloud but adds no new semantic details beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states what the tool returns: a packet for one entity at a specific date, including the entity, pins, relationships, and satellite still. It is specific about the resource and the time dimension, but it does not explicitly differentiate itself from sibling tools like entity_history or entity_change.

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?

The description provides no guidance on when to use this tool versus alternatives such as entity_history or entity_change. It mentions billing prerequisites ('quote first with billing_quote') but that is a process step, not a usage guideline for selecting this tool over others.

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

All GREENLANDAI 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.

Resources

Need Help?