TDQS

reports / d2o2aj9xl8

Perigee

19 tools · specification 1.2 · requested 2026-11-16 15:51:48 UTC

Server

Overall
A4.2definitions 70% · coherence 30%
Definition quality
A3.9mean 4.2 · min 3.5 · 19/19 tools
Coherence
A5.0

The Perigee server demonstrates high coherence with a well-organized, comprehensive set of 19 tools. Each tool has a clear, distinct purpose, consistent naming, and appropriate scope. The only shadow candidate (perigee_distance_series vs perigee_about) does not present genuine overlap, as perigee_about provides metadata about data sources, not distance calculations. Overall, the tool set is exemplary in its design and coverage.

5
DisambiguationEach tool targets a distinct aspect of space observation: finding objects, object facts, state, orbit, passes, sky, events, tonight summary, conjunctions, shadow, ground track, close approach, stats, distance, distance series, view, describe view, definitions, and about. The descriptions clearly delineate boundaries, e.g., perigee_sky for a snapshot vs perigee_tonight for a night summary, and perigee_close_approach for spatial distance vs perigee_sky_conjunctions for angular separation.
5
Naming ConsistencyAll tool names follow a consistent pattern: 'perigee_' prefix followed by a noun or noun phrase (find, object, state, orbit, passes, sky, events, tonight, sky_conjunctions, shadow, ground_track, close_approach, stats, distance, distance_series, view, describe_view, define, about). The naming is uniform, descriptive, and predictable, making it easy for an agent to infer the purpose of each tool.
5
Tool Count AppropriatenessWith 19 tools, the server covers a comprehensive range of space-related queries without being excessive. Each tool serves a distinct function, from basic lookups to specialized calculations and educational content. The count is well-scoped for the domain, providing depth without redundancy.
5
CompletenessThe tool set covers the full lifecycle of space observation: finding objects, retrieving facts, computing state and orbits, predicting passes and events, providing sky views, and offering educational definitions and about information. There are no obvious gaps; even edge cases like shadow prediction and ground tracks are included. The server appears complete for its stated purpose.

Tools

  • perigee_find

    554354A4.4

    This is a well-crafted description that clearly defines the tool's purpose as a name-to-ID resolver, provides explicit usage guidance ('start here'), and adds behavioral context (bilingual support, object scope) beyond the annotations. The schema covers parameters fully, so the description's value is in usage and purpose clarity. It is concise and complete for a simple read-only lookup tool, earning high scores across most dimensions.

    5
    Purpose Clarity · 25%The description clearly states the tool's purpose: 'Looks up objects by name or identifier' and enumerates the types of objects it can find (planets, moons, missions, satellites, sites, stars). It also explicitly distinguishes itself from siblings by noting it 'Returns the ids the other tools take' and advises to 'start here when you only have a name', which differentiates it from the other perigee_* tools that likely operate on known IDs.
    5
    Usage Guidelines · 20%The description provides explicit guidance on when to use this tool: 'start here when you only have a name.' It also implies that this is the entry point for resolving names to IDs, which is a clear usage context. While it doesn't explicitly say 'use this instead of X', the instruction to start here and the mention of returning IDs for other tools effectively communicates the primary use case and distinguishes it from tools that require IDs.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to repeat that. The description adds valuable behavioral context: it supports English and French with optional accents, and it returns IDs that are used by other tools. It also clarifies the scope of objects covered (e.g., 'any active Earth satellite'), which is beyond what annotations provide. However, it doesn't mention potential ambiguity or multiple matches, but that's minor given the annotations.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents both parameters (query and limit) with examples. The description adds some context by explaining that the query can be a name or identifier and lists example types, but it doesn't add much beyond the schema's examples. The limit parameter is not mentioned in the description, but the schema covers it. Thus, the description adds marginal value, so a baseline 3 is appropriate.
    5
    Conciseness & Structure · 10%The description is a single, well-structured sentence that front-loads the core purpose and then lists the object types and the key output (IDs). It is concise, with no wasted words, and every clause adds value. The final sentence 'start here when you only have a name' is a clear, actionable instruction. This is an excellent example of efficient writing.
    4
    Contextual Completeness · 10%Given the tool's simplicity (2 params, no output schema, read-only), the description is quite complete. It covers the input types, the scope of objects, and the output (IDs). The annotations cover safety and open-world aspects. The only minor gap is that it doesn't describe the return format (e.g., list of matches with IDs), but since there is no output schema, a bit more detail could be helpful. However, the description's clarity and the tool's simplicity make it sufficient.
    params
    2 (1 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    1
    bytes
    862
    hash
    b2a6cae20ce2fe53
  • perigee_object

    544344A4.1

    The description is clear and informative, effectively distinguishing the tool from siblings and covering the key return data. It leverages the annotations well and provides adequate parameter context, though it could be more explicit about when to use it versus other perigee tools. Overall, a solid, above-average description.

    5
    Purpose Clarity · 25%The description clearly states the tool returns 'Facts about an object' and enumerates the specific types of facts (name, agency, launch date, identifiers, etc.), distinguishing it from sibling tools like perigee_orbit or perigee_state. The verb 'returns' and the resource 'object facts' are specific and unambiguous.
    4
    Usage Guidelines · 20%The description implies usage for retrieving detailed object information, and the parameter description for 'id' explicitly references perigee_find, indicating a workflow dependency. However, it does not explicitly state when not to use this tool versus alternatives like perigee_state or perigee_orbit, which could be used for specific data needs.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to restate safety. It adds value by disclosing that include_image optionally returns the image itself, and that the tool returns links and credits, which is beyond the schema. No contradictions with annotations.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds minimal extra meaning beyond the schema, such as the fact that include_image returns the image itself, but this is also in the schema. Baseline 3 is appropriate.
    4
    Conciseness & Structure · 10%The description is a single, information-dense sentence that front-loads the core purpose and lists the key data fields. It is efficient, though slightly long due to the enumeration, but every part adds value. No fluff.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (3 params, no output schema), the description covers the main return content and the optional image behavior. It doesn't explain the return format or structure, but with no output schema, that might be a gap. However, the description is sufficient for an agent to understand what it will get.
    params
    3 (1 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    1
    bytes
    1080
    hash
    816d225c6deecabf
  • perigee_state

    544454A4.4

    The description is well-crafted, clearly stating the tool's purpose and output while adding behavioral context beyond the annotations. It effectively differentiates from siblings and provides parameter semantics that complement the schema. Minor gaps include lack of explicit usage exclusions and return format details, but overall it is a high-quality description.

    5
    Purpose Clarity · 25%The description clearly states the tool provides position and velocity vectors in specific reference frames, along with derived quantities like distance, altitude, speed, and ground point. It distinguishes itself from siblings by focusing on state vectors rather than orbital elements or passes, and the title 'Position and velocity' reinforces the purpose.
    4
    Usage Guidelines · 20%The description implies usage for querying the state of an object at a date relative to a centre, with default centre behavior explained. It does not explicitly mention when not to use it or alternatives, but the context of sibling tools (e.g., perigee_orbit for orbital elements) makes the use case clear. The description could be improved by noting that perigee_orbit is for orbital elements, but it's not misleading.
    4
    Behavioral Transparency · 20%Annotations declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to repeat safety. It adds valuable behavioral context: the default centre, the inclusion of light time, sunlight status, and provenance, and the special ground-point data for Earth, Moon, and Mars. This goes beyond the annotations and helps the agent understand the output richness.
    4
    Parameter Semantics · 15%Schema coverage is 100%, so the baseline is 3. The description adds meaning by explaining the default centre behavior and the units (km, km/s) and reference frame (ICRF/J2000), which are not in the schema. It also clarifies the 'id' parameter's role via the example, but the schema already covers that. The description compensates for the schema's lack of unit details, so a 4 is warranted.
    5
    Conciseness & Structure · 10%The description is a single, dense paragraph that front-loads the core output (position and velocity) and then lists additional derived quantities. Every sentence adds value, and it avoids redundancy with the schema. It is concise yet comprehensive, with no wasted words.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (3 params, no output schema), the description covers the essential output fields and special cases (ground point for Earth/Moon/Mars). It doesn't explain the return format or pagination, but since there's no output schema, the description provides enough for an agent to understand what to expect. The lack of explicit return structure is a minor gap, but the description is sufficient for most use cases.
    params
    3 (1 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    1
    bytes
    1201
    hash
    0fbdf0d93452d9d1
  • perigee_orbit

    544344A4.1

    The description is well-crafted, clearly stating the tool's purpose and distinguishing between Earth satellites and other objects. It leverages annotations effectively and provides necessary context for parameters. Minor gaps in explicit usage alternatives and structure, but overall it is a strong, informative description.

    5
    Purpose Clarity · 25%The description clearly states the tool returns orbital elements (perigee/apogee altitudes, period, inclination, eccentricity, semi-major axis) and distinguishes between Earth satellites (mean elements from published element sets) and other objects (instantaneous two-body elements). It differentiates from siblings like perigee_state (likely state vectors) and perigee_ground_track (path).
    4
    Usage Guidelines · 20%The description explains when to use it: for orbital elements, with a note on the difference between Earth satellites and other objects. It doesn't explicitly mention alternatives, but the context of sibling tools (e.g., perigee_state for state vectors) implies the distinction. It lacks explicit 'when not to use' guidance.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to restate safety. It adds valuable context: for Earth satellites it uses mean elements from published element sets, while for other objects it computes instantaneous two-body elements at a date, with default centre and inclination reference. This goes beyond annotations.
    3
    Parameter Semantics · 15%Schema coverage is 100%, so the schema already documents all three parameters. The description adds context for the 'date' parameter (default now) and 'centre' (default body they orbit), but these are also partially in the schema. It doesn't add syntax details beyond what the schema provides, so baseline 3 is appropriate.
    4
    Conciseness & Structure · 10%The description is a single, dense paragraph that packs a lot of information without fluff. It is front-loaded with the core output, then explains the two cases. It could be slightly more structured (e.g., bullet points) but is efficient and readable.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (two distinct behaviors for Earth vs. other objects), the description covers the key distinctions and defaults. No output schema exists, but the description lists the returned elements, which is sufficient. It doesn't mention edge cases like invalid IDs, but that's not required.
    params
    3 (1 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    1
    bytes
    1147
    hash
    4d55a66b6646420d
  • perigee_passes

    554455A4.7

    This is a high-quality tool description that clearly states its purpose, provides explicit usage guidance, and adds behavioral context beyond the annotations. It effectively differentiates itself from siblings and compensates for the lack of an output schema. The only minor gap is that it doesn't detail the exact format of the output, but the description is otherwise exemplary.

    5
    Purpose Clarity · 25%The description clearly states the tool computes satellite pass times (rise, highest point, set) with direction and visibility for a given place, and it distinguishes itself from siblings by noting it does not do geocoding and by pointing to perigee_tonight for whole-night highlights. The verb 'passes over' and the resource 'satellite' are specific and unambiguous.
    5
    Usage Guidelines · 20%The description explicitly tells the agent when to use this tool (for satellite passes over a place) and what inputs are needed (latitude, longitude, time zone). It also provides a clear alternative: 'For the whole night's highlights at once, use perigee_tonight.' This is explicit guidance on when not to use this tool.
    4
    Behavioral Transparency · 20%Annotations declare readOnlyHint=true and openWorldHint=true, which already indicate a safe, read-only operation. The description adds valuable behavioral context: it does not geocode, so the agent must supply coordinates and time zone; it also explains the output includes rise/set times, azimuth, elevation, and visibility conditions. This goes beyond the annotations without contradicting them.
    4
    Parameter Semantics · 15%The schema has 100% coverage, so the baseline is 3. The description adds meaning by explaining the purpose of the parameters (e.g., 'Give the place's latitude and longitude... and its IANA time zone') and clarifies that the 'id' can be a NORAD number or other identifiers, which is not fully explicit in the schema. It also mentions the 10-day limit, which aligns with the 'days' parameter maximum.
    5
    Conciseness & Structure · 10%The description is a single, well-structured paragraph that front-loads the core purpose and then provides essential usage details. Every sentence adds value: it lists example satellite IDs, explains the output, specifies required inputs, and gives a sibling alternative. No fluff or redundancy.
    5
    Contextual Completeness · 10%Given the tool's moderate complexity (9 parameters, no output schema), the description is complete enough. It covers the main use case, required inputs, output content, and a key limitation (no geocoding). The schema already documents all parameters, and the description adds the necessary context for correct invocation. The sibling alternative is also mentioned, making it contextually complete.
    params
    9 (3 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    3
    bytes
    2075
    hash
    ab249a1b620631f8
  • perigee_sky

    554355A4.5

    This is a well-crafted description that clearly defines the tool's purpose, provides explicit usage guidance with alternatives, and adds valuable behavioral context beyond the annotations. It is concise and complete, making it easy for an agent to select and invoke the tool correctly.

    5
    Purpose Clarity · 25%The description clearly states the tool's purpose: to provide a snapshot of the sky from a given place and date, listing specific celestial objects and their properties. It distinguishes itself from siblings by explicitly mentioning perigee_tonight and perigee_events for different use cases.
    5
    Usage Guidelines · 20%The description explicitly states when to use this tool (for a snapshot at one moment) and when not to (for a summary of the coming night or dated events), naming the alternative tools. It also provides a key usage note: the user must supply coordinates because Perigee does no geocoding.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true, so the description doesn't need to restate that. It adds useful behavioral context: the tool returns a snapshot at one moment, does not geocode, and includes only bright named stars above the horizon. This goes beyond the annotations and helps set expectations.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the baseline is 3. The description does not add much parameter-specific detail beyond what the schema provides, but it does mention that coordinates are required and that no geocoding is performed, which reinforces the importance of latitude/longitude. No additional syntax or format details are given, so a 3 is appropriate.
    5
    Conciseness & Structure · 10%The description is a single, well-structured paragraph that front-loads the core purpose and then lists the included data. It is concise, with no redundant or filler sentences, and every sentence adds value.
    5
    Contextual Completeness · 10%Given the tool's moderate complexity (6 parameters, no output schema), the description is complete: it explains what the tool returns, the need for coordinates, and how it differs from related tools. The schema covers all parameters, and the description covers the behavioral aspects, making it sufficient for an agent to use correctly.
    params
    6 (2 required, 100% described)
    annotations
    readOnly=true openWorld=false
    output schema
    no
    cost
    2
    bytes
    1516
    hash
    b0f7cd4209969c5c
  • perigee_events

    554344A4.3

    This is a well-crafted description that clearly defines the tool's purpose, enumerates event types, and explicitly differentiates it from perigee_sky. It provides strong usage guidance and behavioral context, though it relies on the schema for parameter details. The only minor gap is not describing the output structure, but that's acceptable given the read-only nature and schema coverage.

    5
    Purpose Clarity · 25%The description clearly states the tool lists astronomical and mission events over a period, enumerating specific event types (Moon phases, eclipses, equinoxes, etc.) and explicitly distinguishes it from perigee_sky by noting it provides worldwide dates, not what is visible at a given moment. This is a specific verb+resource with clear scope and differentiation from siblings.
    5
    Usage Guidelines · 20%The description explicitly states the default period (next 30 days, max 366), and provides a clear exclusion: 'Worldwide dates, not what is up at a given moment (use perigee_sky).' This names the alternative tool and clarifies when not to use this tool, which is excellent guidance.
    4
    Behavioral Transparency · 20%Annotations declare readOnlyHint=true and openWorldHint=false, so the description doesn't need to restate safety. It adds behavioral context: the default period, the maximum period, and the conditional behavior for eclipses (with a place, it shows how they look and duration). It also clarifies that it returns worldwide dates, not local sky views. This adds value beyond annotations, though it doesn't detail output format or pagination, but that's not critical for a read-only list tool.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents all 7 parameters. The description adds context for the 'days' parameter (default 30, max 366) and the 'kinds' parameter (lists the enum values), but these are also in the schema. It doesn't add new meaning beyond the schema, so baseline 3 is appropriate.
    4
    Conciseness & Structure · 10%The description is a single, dense sentence that front-loads the core purpose and then lists event types. It's efficient but somewhat long; however, every clause adds value (event types, conditional eclipse behavior, and the distinction from perigee_sky). No wasted words, but the length is justified by the complexity.
    4
    Contextual Completeness · 10%Given the tool's complexity (7 optional parameters, many event types, no output schema), the description covers the main use cases and the key distinction from perigee_sky. It doesn't explain return format or how to filter by specific event types beyond the 'kinds' parameter, but the schema covers that. The description is complete enough for an agent to select and invoke correctly.
    params
    7 (0 required, 100% described)
    annotations
    readOnly=true openWorld=false
    output schema
    no
    cost
    0
    bytes
    1678
    hash
    38cc924c6cc31890
  • perigee_tonight

    554344A4.3

    This is a well-crafted description that clearly explains the tool's purpose, usage, and limitations. It effectively differentiates from sibling tools and provides necessary context for the agent. Minor improvements could include structuring the list of included data, but overall it's a strong example.

    5
    Purpose Clarity · 25%The description clearly states the tool's purpose: to provide a comprehensive nightly sky report for a given place, including night start/end, Moon, planets, satellite passes, conjunctions, and events. It explicitly distinguishes itself from sibling tools by naming them and explaining that this tool combines them for a single night.
    5
    Usage Guidelines · 20%The description explicitly states when to use this tool (for a single night's overview) and when to use alternatives ('use those for another moment, another satellite or a longer period'). It also provides clear prerequisites: latitude, longitude, and IANA time zone, and notes that no geocoding is performed.
    4
    Behavioral Transparency · 20%Annotations declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to restate safety. It adds valuable context: the tool aggregates data from four other tools, requires a time zone for local times, and does no geocoding. It doesn't mention output format or pagination, but given the annotations, this is sufficient.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents all parameters. The description adds context about the time zone being required for local times and that no geocoding is done, but it doesn't add syntax or format details beyond the schema. Baseline 3 is appropriate.
    4
    Conciseness & Structure · 10%The description is a single, dense paragraph that front-loads the core purpose and then lists the included data. It's efficient but could be slightly more structured (e.g., bullet points) for readability. Still, every sentence earns its place.
    4
    Contextual Completeness · 10%Given the tool's complexity (aggregating multiple data sources) and the absence of an output schema, the description does a good job of setting expectations. It lists all the data categories and clarifies the scope (one night). It could mention that the output is a text summary, but the description is otherwise complete.
    params
    6 (2 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    2
    bytes
    1600
    hash
    87688fd7ac4505e5
  • perigee_sky_conjunctions

    544454A4.4

    This is a well-crafted description that clearly explains the tool's purpose, distinguishes it from a closely related sibling, and provides essential usage context. It leverages the annotations effectively and adds value beyond the schema, making it a strong example of a helpful tool description.

    5
    Purpose Clarity · 25%The description clearly states the tool finds apparent close pairings (conjunctions) of the Moon, planets, and bright stars, with optional satellite involvement, and explicitly distinguishes from perigee_close_approach by noting it's about angular separation, not physical distance. This is a specific verb+resource with clear scope.
    4
    Usage Guidelines · 20%The description provides clear context on when to use (for apparent close pairings) and explicitly mentions an alternative (perigee_close_approach) for physical distances. It does not explicitly state when not to use, but the distinction is clear enough.
    4
    Behavioral Transparency · 20%Annotations declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to repeat safety. It adds useful behavioral context: default period, max days, satellite-specific behavior (one day), and that it reports visibility and where to look. This goes beyond annotations.
    4
    Parameter Semantics · 15%Schema coverage is 100%, so baseline is 3. The description adds value by explaining the default days (7, or 1 with satellite) and the meaning of max_separation (widest separation kept), which are not fully clear from schema alone. It also clarifies the satellite parameter's role.
    5
    Conciseness & Structure · 10%The description is a single, dense paragraph that front-loads the core purpose and then adds key constraints and alternatives. Every sentence adds value, with no fluff or repetition.
    4
    Contextual Completeness · 10%Given the tool's complexity (9 params, no output schema), the description covers the main use cases, defaults, and the key distinction from a sibling. It doesn't detail return format, but the output schema is absent, so some ambiguity remains; however, the description is sufficient for an agent to understand what it will get.
    params
    9 (2 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    2
    bytes
    1861
    hash
    9e47e34af9162805
  • perigee_shadow

    544354A4.2

    The description is clear, concise, and well-scoped, effectively distinguishing this shadow-analysis tool from its siblings. It leverages annotations well and provides practical context for usage. Minor gaps include lack of explicit alternatives and output format details, but overall it is a strong, high-quality description.

    5
    Purpose Clarity · 25%The description clearly states the tool determines whether an object is in sunlight, penumbra, or umbra, and when it enters/leaves shadow. It specifies the resource (object) and the action (shadow analysis), and distinguishes it from siblings by focusing on shadow events rather than general state or orbit.
    4
    Usage Guidelines · 20%The description explains the default behavior (over two orbits, at most 48 hours) and gives a practical use case (explaining why a satellite fades). It does not explicitly mention alternatives, but the sibling names (e.g., perigee_state, perigee_events) imply this is the shadow-specific tool, and the context is clear enough for an agent to choose it.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to restate safety. It adds useful behavioral context: the default time window (two orbits, max 48 hours) and the fact that it covers Earth, lunar, and Martian orbiters with different shadow-casting bodies. This goes beyond the schema and annotations.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents all six parameters. The description adds context for the 'hours' parameter (default two orbits) and clarifies the 'centre' parameter (body casting the shadow), but these are also partially in the schema. The description doesn't add significant new meaning beyond the schema, so a baseline 3 is appropriate.
    5
    Conciseness & Structure · 10%The description is two sentences, front-loaded with the core purpose, and includes a practical example. Every sentence adds value: the first defines the tool's function and scope, the second explains a common use case. No wasted words.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (6 params, no output schema), the description covers the main behavior and default time window. It doesn't detail the output format, but with no output schema, that's a minor gap. The description is sufficient for an agent to understand what the tool does and when to use it, though it could mention that results include shadow entry/exit times.
    params
    6 (1 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    1
    bytes
    1433
    hash
    9f5bf7917e3451e1
  • perigee_ground_track

    544454A4.4

    This is a well-crafted tool description that clearly states the purpose, output format, and key behavioral details (antimeridian split, point limit). It leverages the schema's thorough parameter documentation and the annotations' safety hints, adding value by explaining the output structure. The only minor gap is the lack of explicit usage guidance versus sibling tools, but the description is otherwise excellent and scores high across all dimensions.

    5
    Purpose Clarity · 25%The description clearly states the tool computes the ground track of an Earth satellite, specifying the output format (list of points and GeoJSON MultiLineString) and the key feature of splitting at the antimeridian. This distinguishes it from sibling tools like perigee_orbit (which likely provides orbital elements) and perigee_state (which likely gives a single state vector). The verb 'compute' or 'return' is implied by the description of the output, making the purpose unambiguous.
    4
    Usage Guidelines · 20%The description implies usage for visualizing satellite ground paths on a map, and the mention of 'ready for a map' gives context. However, it does not explicitly state when to use this tool versus alternatives like perigee_orbit or perigee_state. The sibling list shows many related tools, but no explicit exclusions or alternatives are provided. The description is clear enough for an agent to infer the use case, but lacks explicit guidance on when not to use it.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation. The description adds valuable behavioral details: the output is split at the antimeridian (a non-obvious behavior), the point limit (up to 360 points), and the structure (list of points plus GeoJSON). It does not mention pagination or error conditions, but given the read-only nature and the simplicity of the tool, the description provides sufficient transparency beyond the annotations.
    4
    Parameter Semantics · 15%The input schema already provides detailed descriptions for all 5 parameters, including examples and defaults. The description adds context by explaining the output structure (points and GeoJSON) and the antimeridian split, which helps understand how parameters like 'orbits' and 'points' affect the result. However, the description does not add new parameter-specific semantics beyond what the schema already covers, but it does reinforce the purpose of the parameters in the context of the output. With 100% schema coverage, a baseline of 3 is appropriate, and the description's additional context on output justifies a 4.
    5
    Conciseness & Structure · 10%The description is a single, well-structured sentence that front-loads the core purpose (ground path) and then details the output format and key feature (antimeridian split). It is concise, with no redundant information, and every clause adds value. The mention of 'up to 360 points' is a useful constraint that helps set expectations. This is an example of efficient, high-quality description writing.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (5 parameters, no output schema), the description is quite complete. It explains the output format (points and GeoJSON), the antimeridian handling, and the point limit. The schema covers parameter details, and the annotations cover safety. The only missing piece is a note on the coordinate system (likely WGS84) or the time format, but these are standard and inferable. The description is sufficient for an agent to use the tool correctly without additional context.
    params
    5 (1 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    1
    bytes
    1182
    hash
    65388176f14fcff9
  • perigee_close_approach

    554354A4.4

    This is a well-crafted description that clearly states the tool's purpose, provides explicit usage guidance with a named alternative, and adds behavioral context beyond the annotations. It is concise and complete for the tool's complexity, earning high scores across all dimensions.

    5
    Purpose Clarity · 25%The description clearly states the tool computes the closest distance between two objects in space over a period, with specific details (when, how close, relative speed for Earth satellites). It distinguishes itself from perigee_sky_conjunctions by explicitly noting it measures distance in space, not angular closeness on the sky.
    5
    Usage Guidelines · 20%The description provides explicit usage context: it is for education only, not for collision avoidance, and it explicitly names the alternative tool (perigee_sky_conjunctions) for sky-based conjunctions. This gives clear when-to-use and when-not-to-use guidance.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to restate safety. It adds valuable behavioral context: the tool returns a disclaimer about orbit precision, and it specifies the default and maximum search period (1 day, at most 7). This goes beyond the schema's parameter constraints.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents all parameters. The description adds context about the default period (1 day) and the maximum (7 days), which aligns with the 'days' parameter, but it doesn't add new meaning for other parameters like 'from', 'to', 'start', or 'time_zone'. Baseline 3 is appropriate.
    5
    Conciseness & Structure · 10%The description is concise, front-loaded with the core purpose, and every sentence adds value. It includes a caveat about educational use and a pointer to an alternative tool without any fluff.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (6 parameters, no output schema), the description covers the key aspects: what it does, the time range, the educational caveat, and the distinction from a sibling tool. It doesn't describe the return format, but since there is no output schema, that might be a minor gap. However, the description is sufficient for an agent to select and invoke the tool correctly.
    params
    6 (2 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    2
    bytes
    1281
    hash
    fa5e5a20d27dce7c
  • perigee_stats

    543344A3.9

    The description is clear and well-structured, effectively communicating the tool's purpose and filtering capabilities. It leverages the annotations for safety and open-world hints, and the schema covers parameter details. Minor gaps include lack of explicit usage guidance versus siblings and no mention of return format, but overall it is a solid, above-average description.

    5
    Purpose Clarity · 25%The description clearly states the tool provides counts of active satellites across multiple dimensions (owner, operator, group, orbit regime, etc.), with a specific verb ('Counts') and resource ('active satellites'). It distinguishes itself from sibling tools like perigee_find or perigee_object by focusing on statistics rather than individual object data.
    4
    Usage Guidelines · 20%The description implies usage for retrieving statistical summaries, and the filtering parameters (owner, operator, group) are explained. However, it does not explicitly state when to use this tool versus alternatives (e.g., perigee_find for searching specific satellites), but the context of 'counts' makes it clear enough for most cases.
    3
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation with potentially changing data. The description adds that it provides counts and filtering, but does not disclose details like pagination behavior or whether results are cached. Given the annotations cover the safety profile, a 3 is appropriate.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so all five parameters are documented in the schema. The description adds context by explaining that owner, operator, or group narrow the lists, but does not add syntax or format details beyond what the schema provides. Baseline 3 is correct.
    4
    Conciseness & Structure · 10%The description is a single, information-dense sentence that lists all the dimensions and filtering options. It is efficient and front-loaded with the main purpose. Slight room for improvement in breaking it into shorter sentences, but it is not verbose.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (5 optional parameters, no output schema), the description covers the main functionality and filtering options. It does not explain the return format, but since there is no output schema, the agent might need more detail on what the counts look like. However, the description is sufficient for a statistics tool with read-only annotations.
    params
    5 (0 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    0
    bytes
    1294
    hash
    0df7bc260e07e594
  • perigee_distance

    554354A4.4

    This is a well-crafted description that clearly states the tool's purpose, provides explicit usage guidance with sibling alternatives, and adds behavioral context beyond annotations. It leverages the schema's full parameter coverage and remains concise. Minor gap: no mention of return format, but the description's detail on units and provenance makes it highly effective.

    5
    Purpose Clarity · 25%The description clearly states the tool computes centre-to-centre distance between two objects at a date, including units (km, AU) and light travel time, and mentions provenance. It distinguishes itself from siblings by explicitly naming perigee_distance_series and perigee_close_approach for different use cases.
    5
    Usage Guidelines · 20%The description provides explicit guidance on when to use this tool versus alternatives: 'Over a period, use perigee_distance_series; for the exact closest moment, perigee_close_approach.' This clearly directs the agent to the correct tool for different scenarios.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to restate safety. It adds useful context: the tool returns distance in km and AU, includes light travel time, and provides provenance of positions. It also clarifies it's for a single moment, which is a behavioral trait not in annotations.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents all three parameters. The description adds an example ('from earth to mars') and clarifies the output includes light travel time, but doesn't add significant meaning beyond the schema. Baseline 3 is appropriate.
    5
    Conciseness & Structure · 10%The description is concise, front-loaded with the core purpose, and includes an example and sibling differentiation in just two sentences. Every sentence adds value with no redundancy.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (3 params, no output schema), the description covers the essential aspects: what it computes, units, example, and alternatives. It doesn't explain return format, but the description's mention of km, AU, and light travel time partially compensates. The openWorldHint and readOnlyHint annotations cover safety. Slight gap on return structure, but adequate.
    params
    3 (2 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    2
    bytes
    1240
    hash
    049ae403f33d4da1
  • perigee_distance_series

    554354A4.4

    This is a well-crafted description that clearly states the tool's purpose, differentiates it from the close-approach sibling, and provides usage guidance. It leverages the annotations for safety and adds the key precision limitation. Minor gap: no explicit mention of return format, but the name and context make it inferable. Overall, a high-quality description.

    5
    Purpose Clarity · 25%The description clearly states the tool computes distances between two objects sampled evenly over a period, producing a series with closest and farthest samples. It distinguishes itself from the sibling perigee_close_approach by noting the step limits precision, making the purpose specific and unambiguous.
    5
    Usage Guidelines · 20%The description explicitly says when to use this tool (for a table or chart) and when not to (for exact closest moment, use perigee_close_approach). This provides clear guidance on selecting between the two related tools, which is exactly what the dimension requires.
    4
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to repeat safety. It adds the key behavioral trait that the step limits precision, which is not in the annotations. It could mention that the output is a series (not a single value) but that's implied by the name and description. No contradiction.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents all parameters. The description adds the concept of 'sampled evenly' and 'step limits precision', which gives context to the 'steps' parameter, but it doesn't add syntax or format details beyond the schema. Baseline 3 is appropriate.
    5
    Conciseness & Structure · 10%The description is two sentences, front-loaded with the core purpose, and every word earns its place. It efficiently conveys the sampling nature and the precision limitation without fluff.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (5 params, no output schema), the description covers the essential purpose, usage context, and a key limitation. It doesn't describe the return format, but the output is likely a series of distances, which is implied. The sibling differentiation is strong, making it complete enough for an agent to select and invoke correctly.
    params
    5 (4 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    4
    bytes
    1303
    hash
    4bec5a8811544655
  • perigee_view

    544344A4.1

    The description is well-crafted, clearly explaining the tool's purpose and embedding capabilities, with good coverage of special cases. It aligns with annotations and leverages the schema's full parameter documentation. Minor gaps include lack of explicit usage exclusions and some structural improvements, but overall it is highly effective.

    5
    Purpose Clarity · 25%The description clearly states the tool's purpose: to link or embed a 3D view of an object, with options for date, playback, and following. It distinguishes itself from siblings by focusing on embedding and linking, and it mentions the star_map special case, which adds specificity.
    4
    Usage Guidelines · 20%The description explains when to use this tool (to link or embed a view) and provides context for the star_map case, but it does not explicitly state when not to use it or mention alternatives. It implies usage for embedding in lesson pages, which is clear enough.
    4
    Behavioral Transparency · 20%Annotations declare readOnlyHint=true, and the description aligns with that (it's a view/link tool, no mutations). The description adds useful behavioral context: the iframe can be driven via postMessage, and star_map changes the view to show the Sun. It does not contradict annotations.
    3
    Parameter Semantics · 15%Schema description coverage is 100%, so the schema already documents all parameters. The description adds some context (e.g., postMessage protocol, star_map behavior) but does not add much beyond the schema for individual parameters. Baseline 3 is appropriate.
    4
    Conciseness & Structure · 10%The description is a single paragraph but packs a lot of information efficiently. It is front-loaded with the main purpose and then details the embedding capabilities. It could be slightly more structured, but it is not verbose.
    4
    Contextual Completeness · 10%Given the tool's complexity (9 parameters, special cases like star_map), the description covers the key behaviors: linking, embedding, postMessage control, and star_map exception. It lacks details on return values, but there is no output schema, and the description is sufficient for an agent to use it correctly.
    params
    9 (1 required, 100% described)
    annotations
    readOnly=true openWorld=false
    output schema
    no
    cost
    1
    bytes
    1877
    hash
    d55366bec5eb9551
  • perigee_describe_view

    544344A4.1

    The description is well-crafted, clearly stating the tool's purpose and output, with useful behavioral details like the exclusion of camera framing. It aligns with the read-only and open-world annotations. Minor gaps exist in explicit usage guidelines and parameter semantics, but overall it is a strong description that would help an agent select and invoke the tool correctly.

    5
    Purpose Clarity · 25%The description clearly states the tool's purpose: converting a Perigee link or embed URL into descriptive text. It specifies the input (link or embed URL) and the output (alternative text and lesson notes), and distinguishes it from sibling tools like perigee_view (which likely creates the view) by focusing on describing an existing view.
    4
    Usage Guidelines · 20%The description implies when to use this tool: when you have a Perigee link or embed URL and need a textual description. It does not explicitly state when not to use it or mention alternatives, but the context is clear enough for an agent to infer appropriate usage.
    4
    Behavioral Transparency · 20%Annotations indicate readOnlyHint=true and openWorldHint=true, which the description does not contradict. The description adds valuable behavioral context: it explains what the output includes (view, selected object, position reliability, date, speed, frame, filters, hidden elements) and explicitly notes that camera framing is not included, which is a useful limitation.
    3
    Parameter Semantics · 15%The schema already provides descriptions for all three parameters (url, lang, time_zone) with 100% coverage. The description does not add much beyond what the schema states, but it does clarify that the URL can be from perigee_view or a shared link, which is a slight enhancement. Baseline 3 is appropriate.
    4
    Conciseness & Structure · 10%The description is a single, dense sentence that packs a lot of information without being overly verbose. It is front-loaded with the core purpose and then details the output components. It could be slightly more structured (e.g., bullet points) but is efficient and readable.
    4
    Contextual Completeness · 10%Given the tool's moderate complexity (3 params, no output schema), the description covers the essential aspects: input, output, and a key limitation (camera framing not included). It does not explain the return format in detail, but since there is no output schema, the description's mention of 'one-sentence alternative text' and 'description for lesson notes' provides sufficient context.
    params
    3 (1 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    1
    bytes
    986
    hash
    90bd4f387a69fe77
  • perigee_define

    433344A3.5

    The description is clear and concise, effectively communicating the tool's purpose and the key behavior of listing all terms when omitted. It leverages the schema for parameter details and aligns with the read-only annotation. Minor gaps include lack of explicit alternative tool guidance, but overall it's a solid, usable description.

    4
    Purpose Clarity · 25%The description clearly states the tool defines student-level terms shown in Perigee, listing specific examples. It distinguishes from siblings by focusing on definitions rather than data lookups, though it doesn't explicitly name alternatives.
    3
    Usage Guidelines · 20%The description implies usage: provide a term to define, or omit to list all terms. It doesn't explicitly state when to use this over other tools, but the purpose is clear enough that an agent can infer it's for educational definitions.
    3
    Behavioral Transparency · 20%Annotations already declare readOnlyHint=true, so the description doesn't need to state safety. It adds context about the educational level (secondary school) and that omitting the term lists all terms, which is useful. No contradictions.
    3
    Parameter Semantics · 15%Schema coverage is 100%, so the schema already documents both parameters. The description adds the behavior of omitting the term (lists all), which is helpful, but doesn't add much beyond that. Baseline 3 is appropriate.
    4
    Conciseness & Structure · 10%The description is a single sentence, front-loaded with the core purpose. It includes a list of example terms and a clear conditional behavior. No wasted words, though the ellipsis and encoding artifact slightly reduce polish.
    4
    Contextual Completeness · 10%Given the tool's simplicity (2 optional params, no output schema, read-only), the description covers the essential behavior: defining terms and listing all when no term is given. It's complete enough for an agent to use correctly.
    params
    2 (0 required, 100% described)
    annotations
    readOnly=true openWorld=false
    output schema
    no
    cost
    0
    bytes
    714
    hash
    94400a6adb4a0009
  • perigee_about

    434454A3.9

    This is a well-crafted description for a simple informational tool. It clearly states the purpose and content, is concise, and complements the annotations without contradicting them. The only minor gap is the lack of explicit usage guidance, but given the tool's nature, it is not a significant issue.

    4
    Purpose Clarity · 25%The description clearly states the tool's purpose: to provide information about data sources, models, accuracy, catalogue sizes, frame, attribution, and disclaimer. It uses a specific noun phrase ('what every answer rests on') that conveys the tool's role as a meta-informational resource. While it doesn't explicitly distinguish from siblings, the content is unique enough that an agent would understand it's about the system's underlying data and models, not about specific celestial objects or events.
    3
    Usage Guidelines · 20%The description implies that this tool should be used when one needs background information on data sources and model accuracy, but it does not explicitly state when to use it versus alternatives. It doesn't mention any exclusions or alternatives, but the context of sibling tools (all about specific astronomical queries) makes it clear this is the 'about' tool. The guidance is adequate but not explicit.
    4
    Behavioral Transparency · 20%The annotations declare readOnlyHint=true and openWorldHint=true, which already indicate a safe, read-only operation. The description adds value by specifying the exact content areas (data sources, fetch times, models, accuracy, catalogue sizes, frame, attribution, disclaimer), which goes beyond the annotations. It also mentions the educational-use disclaimer, which is a behavioral trait (the tool provides a disclaimer). No contradiction with annotations.
    4
    Parameter Semantics · 15%The tool has zero parameters, so the description doesn't need to explain any. The schema is empty, and the description fully covers what the tool returns. Since there are no parameters, a baseline of 4 is appropriate, and the description does not need to compensate for any schema gaps.
    5
    Conciseness & Structure · 10%The description is a single, well-structured sentence that front-loads the purpose ('What every answer rests on') and then lists the key content areas. It is concise, with no wasted words, and every element adds value. The colon and list format make it scannable.
    4
    Contextual Completeness · 10%Given that the tool has no parameters, no output schema, and simple annotations, the description is quite complete. It covers the main content areas and the disclaimer. It could potentially mention the format of the output (e.g., a text summary) but that is not critical. The description is sufficient for an agent to understand what to expect.
    params
    0 (0 required, 100% described)
    annotations
    readOnly=true openWorld=true
    output schema
    no
    cost
    0
    bytes
    384
    hash
    c4c9b04c6aae2bf3

Deterministic findings

  • warningperigee_distance_series shadow-candidateperigee_distance_series (invocation cost 4) may be shadowed by perigee_about (cost 0): if both can answer the same question, an agent tends toward the cheaper call. Only the coherence evaluation can confirm the purposes overlap; if they do, make them disjoint and say so in both descriptions, or collapse the pair.
  • infoperigee_find no-output-schemaperigee_find has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_object no-output-schemaperigee_object has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_state no-output-schemaperigee_state has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_orbit no-output-schemaperigee_orbit has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_passes no-output-schemaperigee_passes has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_sky no-output-schemaperigee_sky has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_events no-output-schemaperigee_events has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_tonight no-output-schemaperigee_tonight has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_sky_conjunctions no-output-schemaperigee_sky_conjunctions has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_shadow no-output-schemaperigee_shadow has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_ground_track no-output-schemaperigee_ground_track has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_close_approach no-output-schemaperigee_close_approach has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_stats no-output-schemaperigee_stats has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_distance no-output-schemaperigee_distance has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_distance_series no-output-schemaperigee_distance_series has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_view no-output-schemaperigee_view has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_describe_view no-output-schemaperigee_describe_view has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_define no-output-schemaperigee_define has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.
  • infoperigee_about no-output-schemaperigee_about has no output schema, so the description has to explain return values itself. Providing one lets the description spend those words elsewhere.

Share

The badge shows the overall tier and score, and links here. The JSON is the same report the CLI's hosted mode prints.

README badge
[![TDQS](https://tdqs.dev/reports/d2o2aj9xl8/badge.svg)](https://tdqs.dev/reports/d2o2aj9xl8)
Report as JSON

Automate

The same check from a terminal, a CI job or a script, with an API key from your account. Submitting spends one of the account's daily calls; reading the result spends nothing.

The exit code is the verdict, so the command is the gate. A stdio command or a server URL can stand in for the file.

export TDQS_API_KEY=tdqs_...

# exit code 1 below B, so the command is the gate; uvx runs the same command from PyPI
npx mcp-tdqs score --file tools.json --hosted https://tdqs.dev --fail-under B
Command line reference