Skip to main content
Glama

look_from

Read-only

Map pins near a point (lat/lng + radius_km). entity_type alone filters to that type; with id it anchors the view at that entity. Each pin carries its source_tier provenance. Metered: see CHARGING in the server instructions; quote first with billing_quote.

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

Input Schema

NameRequiredDescriptionDefault
idNoEntity id to anchor the pose on (with entity_type).
latNoLatitude in decimal degrees, -90 to 90 (WGS84). Use with lng, or pose on an entity instead.
lngNoLongitude in decimal degrees, -180 to 180 (WGS84).
energyNoInclude energy-fleet infrastructure (power plants and grid assets). Default false.
fieldsNoOnly these keys in each row (plus id). Omit for all.
radius_kmNoSearch radius around the pose, in km. Default 100.
entity_typeNoEntity kind: deposit | infrastructure | company | project.
include_country_centroidsNoAlso return country-centre placeholder pins (entities known only by country). Default false.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • removedInput schema / properties / energy / title
      Removed value: -"Energy"
    • removedInput schema / properties / entity_type / default
      Removed value: -null
    • changedInput schema / properties / entity_type / description
      Previous value: -"Entity kind: deposit | infrastructure | company | project. Alone (with lat/lng) it FILTERS the frame to that type; with `id` it ANCHORS the pose on that entity and keeps all types."New value: +"Entity kind: deposit | infrastructure | company | project."
    • removedInput schema / properties / entity_type / title
      Removed value: -"Entity Type"
    • addedInput schema / properties / fields
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Only these keys in each row (plus id). Omit for all."
      +}
    • removedInput schema / properties / id / default
      Removed value: -null
    • removedInput schema / properties / id / title
      Removed value: -"Id"
    • removedInput schema / properties / include_country_centroids / title
      Removed value: -"Include Country Centroids"
    • removedInput schema / properties / lat / default
      Removed value: -null
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • removedInput schema / properties / lng / default
      Removed value: -null
    • removedInput schema / properties / lng / title
      Removed value: -"Lng"
    • removedInput schema / properties / radius_km / title
      Removed value: -"Radius Km"
    • removedInput schema / title
      Removed value: -"look_fromArguments"
    • removedOutput schema / title
      Removed value: -"look_fromDictOutput"
  2. Changed1 schema field changed
    • changedInput schema / properties / id / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed7 schema fields changed
    • addedInput schema / properties / energy / description
      Added value: +"Include energy-fleet infrastructure (power plants and grid assets). Default false."
    • addedInput schema / properties / entity_type / description
      Added value: +"Entity kind: deposit | infrastructure | company | project. Alone (with lat/lng) it FILTERS the frame to that type; with `id` it ANCHORS the pose on that entity and keeps all types."
    • addedInput schema / properties / id / description
      Added value: +"Entity id to anchor the pose on (with entity_type)."
    • addedInput schema / properties / include_country_centroids / description
      Added value: +"Also return country-centre placeholder pins (entities known only by country). Default false."
    • addedInput schema / properties / lat / description
      Added value: +"Latitude in decimal degrees, -90 to 90 (WGS84). Use with lng, or pose on an entity instead."
    • addedInput schema / properties / lng / description
      Added value: +"Longitude in decimal degrees, -180 to 180 (WGS84)."
    • addedInput schema / properties / radius_km / description
      Added value: +"Search radius around the pose, in km. Default 100."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "look_fromDictOutput",
      +  "type": "object"
      +}
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral context beyond them: the call is metered, must be pre-quoted via billing_quote, and each pin carries source_tier provenance. The only gap is that it defers cost details to server instructions rather than stating them inline.

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?

Four short clauses, front-loaded with the pose mechanism, then the mode rule, then provenance, then cost. Nothing is padded, though the CHARGING pointer is slightly elliptical and requires the agent to go look elsewhere.

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

Completeness5/5

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

With an output schema present, return shape needs no explanation, and all 8 parameters are schema-documented. The description still covers the mode logic, provenance, and the billing precondition — everything an agent needs to invoke it correctly. Zero required parameters is handled by the implicit pose rule (lat/lng or id+entity_type).

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?

Schema coverage is 100%, so baseline is 3, but the description adds cross-parameter semantics the schema does not: entity_type alone acts as a filter, while supplying id together with entity_type anchors the pose on that entity. That interaction rule is exactly the kind of meaning a schema of independent property descriptions cannot convey.

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 verb+resource ('Map pins near a point') with the pose mechanism (lat/lng + radius_km), which is far more informative than the bare name. It does not, however, distinguish itself from closely related siblings like look_at, look_through, map_viewport, or nearby, so an agent still has to guess which view tool to pick.

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?

Gives clear conditional usage for the two modes ('entity_type alone filters... with id it anchors'), which is genuinely useful. It also states a workflow prerequisite (quote first with billing_quote). But it never says when to choose this over the sibling view/nearby tools, which is the harder decision for an agent.

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