Skip to main content
Glama
Sign In
infrontofx-fivem

infrontofx-fivem

by baespy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_infrontofx_topics

Read-onlyIdempotent

Lists FiveM guidance topics aligned with the active skill so you can choose the right reference before writing, debugging, or reviewing resources.

Instructions

List FiveM guidance topics aligned with infrontofx-skill.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds only the vague 'aligned with infrontofx-skill' scoping note and says nothing about what a topic contains, ordering, or pagination — notable since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no filler. The resource and scope come first, and nothing is redundant.

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?

With no params and no output schema, the description must carry the burden of explaining the return shape, and 'topics' is only loosely indicative. It is adequate for a trivial list call but leaves the agent guessing what each topic entry looks like.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no filtering or input is required, consistent with the empty 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?

Names a specific verb (List) and resource (FiveM guidance topics) and adds a scoping qualifier ('aligned with infrontofx-skill'). However, it does not distinguish this from siblings like get_infrontofx_guidance or get_infrontofx_skill, so an agent cannot tell from the description alone which listing 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 Guidelines2/5

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

There is no statement of when to use this versus the many sibling *infrontofx*/guidance tools, and no noted prerequisites. The phrase 'aligned with infrontofx-skill' hints at a relation but gives no actionable selection rule.

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

Deploy Server

Other Tools